Import set failures
Quick answer
Diagnose failed and partial imports: staging rows, transform errors, coalesce problems and skipped records.
Key takeaways
- Check import row state, then transform history, then target record
- Empty coalesce values create duplicates
- Reference resolution failures leave blank fields, not errors
- Alert on transform errors, do not rely on someone checking
Follow the row
Every import lands in a staging table row with a state. Open the import set, then the row, then the transform history. That path answers most questions in two minutes without guessing.
Common causes
Four issues cover the majority of failures.
- Coalesce field empty in the source, which creates instead of updates
- Reference field cannot resolve the incoming value, so the field ends up empty
- Date format mismatch between the source and the instance format
- Mandatory field on the target table blocking insert, visible in the transform log
Making failures visible
Silent partial imports are the dangerous ones. Add an onComplete transform script that counts errors and raises an event, then notify the integration owner. A daily import that quietly stopped three weeks ago is a data quality incident waiting to happen.
Want to learn this properly?
Our live, instructor-led ServiceNow Training covers this hands-on, with real projects and a certification path.
Check your understanding
What causes duplicate target records on every run?
- A. Missing index
- B. Coalesce field empty or unstable
- C. Wrong table
- D. Too many rows
Show answer
B. Coalesce field empty or unstable
Without a reliable coalesce value the transform inserts instead of updating.
What is the fastest diagnostic path?
- A. System logs
- B. Import set row then transform history
- C. Email log
- D. ACL debug
Show answer
B. Import set row then transform history
The row and its transform history name the failure directly.