Resolving Duplicate Records in ServiceNow Import Sets: Unique Index Solution
A large enterprise is importing 500,000 asset records from an external inventory system using a scheduled data import into the alm_asset table. The transform map uses a coalesce on the 'asset_tag' field to match existing records. The 'asset_tag' field in the target table is a string field with a unique index. The import set table has no unique index on any field. The transform map has 'Enable Duplicate Detection' checked. After the first import, the team notices that many duplicate records were created instead of updating existing ones. There are no errors in the import log. The source data contains only unique asset_tag values. What is the most likely cause of the duplicates?
Quick Answer
This scenario hinges on a distinction many people miss: the unique index on the target table (alm_asset) has nothing to do with duplicate detection during the import itself; that mechanism actually depends on a unique index existing on the import set table, the staging table that holds the raw imported rows before the transform map processes them. Enabling 'Duplicate Detection' on the transform map and coalescing on asset_tag tells ServiceNow which field to match against existing target records, but without a unique index on that same field in the import set table, the system has no reliable way to recognize when it is looking at data it has already staged, so it inserts new records instead of updating existing ones even though the source data itself contains no duplicate values. The other explanations in this scenario are already ruled out directly by the facts given: the source values are confirmed unique, the checkbox is confirmed enabled, and the coalesce field is confirmed correctly mapped, which is exactly why the missing index is the only remaining explanation. When a question describes an import behaving as though duplicate detection simply is not working, despite the coalesce and checkbox settings being correct, check whether the required unique index exists on the import set table itself, since that staging-level index is the piece of the mechanism that is easy to overlook.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The import set table lacks a unique index on the 'asset_tag' field.
The import set table lacks a unique index on the 'asset_tag' field. For duplicate detection to work properly during an import, the import set table must have a unique index on the coalesce field (here 'asset_tag'). Without that index, the system cannot detect duplicates within the same import set, causing multiple records to be inserted instead of updated. Option A is incorrect because the source data contains unique asset_tag values, so case differences are not the issue. Option B is incorrect because the 'Enable Duplicate Detection' checkbox is checked, so it is configured. Option D is incorrect because the coalesce field mapping is correctly set to 'asset_tag'.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The source data contains multiple records with the same 'asset_tag' but different case.
Why it's wrong here
Incorrect: The source data is stated to have unique asset_tag values, so case variation is not the cause.
- ✗
The 'Enable Duplicate Detection' checkbox is not properly configured.
Why it's wrong here
Incorrect: The scenario states it is checked, and the feature is correctly enabled.
- ✓
The import set table lacks a unique index on the 'asset_tag' field.
Why this is correct
Correct: A unique index on the import set table is required for the duplicate detection mechanism to work within the import set; without it, duplicates can be created.
- ✗
The coalesce field mapping is incorrectly mapped to the 'asset_tag' field.
Why it's wrong here
Incorrect: If the mapping were incorrect, the import would likely fail or not update, but duplicates would not be created in such large numbers.
Go deeper
Related to this question
About these practice questions
Courseiva writes every SNOW-CAD question from scratch — 481 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 more ways this is tested on SNOW-CAD
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Which TWO conditions must be met for a transform map to automatically ignore duplicate records during an import?
medium- A.The source table has a unique index on the coalesce field.
- ✓ B.The target table has a unique index on the coalesce field.
- C.The coalesce field mapping uses the 'Ignore if Empty' checkbox.
- D.The import set table has a unique index on the coalesce field.
- ✓ E.The transform map has 'Enable Duplicate Detection' set to true.
Why B: For duplicate detection to automatically ignore duplicate records already in the target table, two conditions must be met: the transform map must have 'Enable Duplicate Detection' set to true (option E), and the target table must have a unique index on the coalesce field (option B). The coalesce field mapping identifies the field used to check for duplicates; a unique index on the target table enforces uniqueness, allowing the system to detect that a record already exists. Options A, C, and D are incorrect: a unique index on the source table (A) is not required for target duplicate detection; the 'Ignore if Empty' checkbox (C) relates to handling empty values, not duplicate detection; and an index on the import set table (D) is used for detecting duplicates within the same import set, not for ignoring duplicates already in the target.
Variation 2. An import set is failing because some records have duplicate values in a unique field. The requirement is to skip duplicates and import only new records. Which transform map option should be used?
easy- A.Enable 'Import set update only' in the transform map.
- B.Enable 'Update existing records' in the transform map.
- C.Enable 'Reject duplicates' in the data source options.
- ✓ D.Enable 'Coalesce' on the unique field and set 'Action' to 'Insert' in the transform map.
Why D: Coalesce on the unique field allows the transform map to identify existing records by matching the incoming field to a unique field in the target table. Setting the Action to 'Insert' ensures that only new records are imported; if a match is found, the record is skipped (since it already exists). Option A ('Import set update only') is not a standard option in ServiceNow. Option B ('Update existing records') would update duplicates rather than skip them. Option C ('Reject duplicates') is not a typical option in data sources; the correct approach is using coalesce with Insert action.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SNOW-CAD practice question is part of Courseiva's free ServiceNow certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SNOW-CAD exam.