Understand the pipeline before configuring a match
Defines where and how external data is retrieved.
Loads source rows into a staging table.
Maps and converts staged fields to a target.
Receives inserted or updated application records.
If the question asks where raw rows wait, choose the Import Set table. If it asks how fields move to the target, choose the Transform Map. If it asks how an existing record is found, inspect coalesce.
Import Set: a controlled staging area
Import Sets bring data from sources such as files, JDBC connections and integrations into an import-set table. Staging preserves incoming values and gives administrators a place to inspect row quality without writing raw source data directly into a business table.
Source evidence
See the actual value that arrived, including blanks and formatting.
Run history
Relate rows to an execution and inspect processing state or errors.
Separation
Keep extraction and staging distinct from target mapping.
An Import Set alone does not define target-field relationships. That responsibility belongs to a Transform Map.
Transform Map: source-to-target mapping and conversion
A Transform Map connects one import-set table to one target table. Field maps relate source columns to target fields. Administrators can use automatic mapping, Mapping Assist, source scripts and transform-event scripts when declarative mapping is insufficient.
u_employee_id=E1042u_employee_id → employee_numberPrefer clear field maps over unnecessary scripts because declarative mappings are easier to test and maintain.
Coalesce: choose update versus insert with a stable key
When a source field map is marked coalesce, the transform searches the target for a record whose target field matches the incoming value. A match normally results in an update; no match normally results in an insert.
employee_number = E1042Choose an immutable source-system identifier when possible. Names, email addresses and departments can change and may not be unique. If multiple fields coalesce, their combined values must consistently identify the target.
It guides the current transform’s match decision. Existing duplicates require separate analysis and controlled remediation.
Worked scenario: nightly employee file creates duplicates
Situation: HR sends a nightly CSV. The Transform Map coalesces on email. Employees who change email receive a second user record instead of an update.
Email changed
The incoming value no longer matches the old target email.
Stable ID exists
The file contains an employee number that remains constant.
Use employee number
Validate uniqueness, coalesce on it and map email as an updateable field.
Test representative inserts and updates outside production, review outcomes, reconcile existing duplicates under approval, and monitor the next scheduled import.
Duplicate import troubleshooting sequence
- Inspect the staged row: verify the key arrived and uses the expected format.
- Inspect the field map: confirm source, target and coalesce configuration.
- Query the target: check changing values, formatting and existing duplicates.
- Review transform history: determine whether the row inserted, updated, ignored or failed.
- Check active maps and schedules: identify another process creating records.
- Review scripts and business rules: locate logic that changes keys or creates related records.
“Coalesce is checked” is not proof that matching works. Source values, target data, map configuration and other writers must agree.
A safe production import process
Measure blanks, duplicates and invalid references.
Document conversions and the stable key.
Cover insert, update, blank-key and invalid-value cases.
Compare expected and actual row outcomes.
Define backup and rollback or repair methods.
Track scheduled runs and outcome changes.
Practice checks with explanations
Where are spreadsheet rows stored before they become incident records?
Best answer: an Import Set table—the staging layer for external rows.
What maps u_caller_email to caller_id?
Best answer: a Transform Map field map and its reference behavior or script.
What determines whether an incoming asset updates instead of inserts?
Best answer: coalesce matching on a stable, correctly mapped identifier.
Common ServiceNow CSA mistakes
- Calling the Import Set the final target.
- Calling coalesce a separate table or engine.
- Coalescing on mutable display values.
- Assuming coalesce repairs old duplicates.
- Testing inserts but not updates.
- Ignoring blank keys and formatting differences.
- Adding scripts before checking standard field maps.
Data Source: where and how rows are retrieved
A ServiceNow Data Source describes the incoming system and retrieval method. It loads rows into an import-set staging table; it does not decide which production fields receive those values.
Scheduled Data Import: connect retrieval, transformation and timing
A scheduled import joins a Data Source to one or more Transform Maps and defines when the job runs. Review the run-as user, frequency, optional condition, pre-import script, post-import script and transform order before enabling it.
- Use daily, weekly, monthly or periodic timing when the source has a predictable delivery window.
- Use After Parent Runs when one import depends on another import completing first.
- Avoid scheduling competing imports for the same time unless concurrency and target-table behavior have been tested.
- Use Execution Contexts to inspect scheduled or concurrent flow when a run behaves intermittently.
Coalesce options and edge cases
If a coalesce query finds more than one target record, the transform updates only the first match. Treat that as a target-data quality problem, not a reliable matching strategy.
Use run evidence to isolate the failed layer
Import Set Runs summarize inserted, updated, ignored, skipped and errored rows. Open row details to inspect state, target-record links, errors and comments; use the Import Log for messages spanning source loading and transformation.
Frequently asked questions
What does a ServiceNow Data Source define?
A Data Source defines where and how ServiceNow retrieves incoming data, such as a file, JDBC connection, LDAP source, REST integration, Data Stream action or custom load script. The retrieved rows are loaded into an import-set staging table before transformation.
What is an Import Set in ServiceNow?
An Import Set stages data from an external source in an import-set table. It separates incoming rows from production target tables so the data can be reviewed and transformed.
What does a Transform Map do?
A Transform Map defines how fields from an import-set source table map to a target table. It can include field maps, scripts, choice handling, reference behavior and transform-event logic.
What does coalesce mean in a ServiceNow Transform Map?
A coalesce field is used to find an existing target record. If a matching record is found, the transform updates it; otherwise, the transform normally inserts a new record.
What happens when multiple fields are marked coalesce?
The transform uses the coalesce fields together to identify a target match. Choose a combination that is stable, populated and genuinely unique in the source and target.
Why can duplicates still appear when coalesce is enabled?
Common causes include blank or inconsistent source keys, mapping the wrong field, changing identifiers, formatting differences, pre-existing duplicates, multiple transform maps or another process creating records.
Where can I troubleshoot a ServiceNow import run?
Start with the import set execution or run details, then inspect row states, target-record links, errors and comments. Use the Import Log for messages across source loading and transformation, and Execution Contexts for scheduled or concurrent import flow.
Official ServiceNow references
Review ServiceNow’s Zurich documentation for Data Sources, Import Sets, Transform Maps, coalesce, scheduled imports and import run details. Validate behavior in the target release and instance.