When importing data into ServiceNow via an Import Set, the system determines whether to update existing records or create new ones based on the Coalesce field setting.
Behavior When No Coalesce Field is Specified:
If no Coalesce Field is defined, ServiceNow treats every imported row as a new record.
The import process does not check for existing records, meaning no records in the target table are updated.
This can result in duplicate entries if the imported data includes records that already exist in the target table.
How Coalescing Works:
A Coalesce Field is used to match incoming data to existing records.
If a matching record is found, it is updated instead of inserting a new one.
If no matching record is found, a new record is created.
Incorrect Answers
A . All rows are rejected from the import, as coalesce field is required ❌ This is incorrect because the import does not require a coalesce field to proceed. The system will still import all rows.
C . Duplicate rows are rejected from the import ❌
Without a coalesce field, duplicates are not rejected. Instead, every row is inserted as a new record, even if it already exists in the target table.
D . All rows are treated as new records, but errors will be flagged in the import log ❌ Errors are only flagged in cases of data mismatches, validation failures, or incorrect mappings, not just because coalescing is missing.
Reference from Certified System Administrator (CSA) Documentation:
ServiceNow Documentation → "Importing Data - Coalescing Best Practices" ServiceNow Import Set Documentation → "Understanding Import Set Behavior Without Coalescing"