Best Practice for Mapping Reference Fields During CSV Import
A company needs to import user records from a CSV file into the User [sys_user] table. The file contains a 'department' column that should map to the 'department' field in ServiceNow. However, the department values in the CSV are full names (e.g., 'Human Resources'), but the department field in ServiceNow uses a reference to the Department [cmn_department] table. What is the best practice for handling this import?
Quick Answer
The answer is to create a transform map that maps the source field to the target field, and use a field mapping script to convert the department name to the correct sys_id. This is the best practice because when importing a CSV with reference field mapping, the transform map processes each row through the Import Set Row table, and a field mapping script can perform a lookup to translate the human-readable department name into the corresponding sys_id from the Department [cmn_department] table. On the ServiceNow CSA exam, this scenario tests your understanding that reference fields store sys_ids, not display values, and that transform maps are the correct mechanism for handling such conversions—a common trap is assuming you can simply map the name directly or use a default value. Remember the memory tip: "Transform maps translate text to ID; scripts make the lookup tidy."
⚠ Common exam trap
Many exam-takers confuse a before business rule (which runs after insert) with a transform script (which runs during import), leading them to choose option A instead of recognizing that transform maps are the correct declarative tool for reference field lookups.
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
✓
Create a transform map that maps the source field to the target field, and use a field mapping script to convert the department name to the correct sys_id.
Import Set Rows are processed through transform maps, which allow field mapping scripts to convert source values (like 'Human Resources') into the corresponding sys_id in the Department [cmn_department] table. This is the standard, supported approach for handling reference field lookups during imports, ensuring data integrity without manual intervention or post-insert processing.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use a before business rule on the User table to convert the department name after the record is inserted.
Why it's wrong here
Business rules run after insert, not during mapping.
- ✓
Create a transform map that maps the source field to the target field, and use a field mapping script to convert the department name to the correct sys_id.
Why this is correct
This is the standard method to handle reference field mapping during import.
- ✗
Use the Import Set Row API to programmatically map the values during import.
Why it's wrong here
The API inserts raw data; mapping is done via transform map.
- ✗
Manually edit the CSV file to replace department names with the corresponding sys_id values.
Why it's wrong here
Manual editing is not scalable and error-prone.
Go deeper
Related to this question
About these practice questions
This SNOW-CSA question is part of Courseiva's 504-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on SNOW-CSA
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. A transform map for importing incidents uses a co-paste field mapping for 'short_description' that references the source field 'caller_id'. The import fails with the error shown. What is the most likely cause?
hard- A.The 'caller_id' field in the target table is read-only
- ✓ B.The import set does not contain a column named 'caller_id'
- C.The target table 'incident' does not have a 'caller_id' field
- D.The co-paste function cannot combine more than two fields
Why B: The error indicates that the transform map is trying to reference a source field named 'caller_id' via a co-paste field mapping, but the import set table does not contain a column with that name. Co-paste mappings combine source fields from the import set row, so if 'caller_id' is missing from the import set columns, the transform engine cannot find the data and fails. Option B correctly identifies that the import set lacks the required column.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SNOW-CSA 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-CSA exam.