InServiceNow, anImport Set Tableis atemporary staging areawhere raw data is storedbefore it is transformed and moved into a target table. It is primarily used indata import processesto ensure data integrity and allow transformation before committing data to production tables.
Stores incoming data from external sources(e.g., CSV files, Excel files, APIs, LDAP, etc.).
Acts as a temporary staging areabefore records are mapped and transformed into atarget table(e.g.,incident,cmdb_ci,problem).
Allows validation and error handlingbefore final data migration.
Uses Transform Mapsto determine how fields in the import set relate to fields in the target table.
Key Functions of an Import Set Table:
Data is importedinto anImport Set Tablefrom an external source.
TheImport Set Table temporarily stores the datawithout affecting existing records.
ATransform Mapis applied to move and modify the data before inserting it into the correct table.
Once transformation is complete, the data is transferred to thetarget table, and the Import Set Table can be cleared.
Example Workflow of an Import Set:
(A) A table where data will be placed, post-transformation – Incorrect
Thetarget table(e.g.,incident,cmdb_ci,problem) holds the dataaftertransformation.
TheImport Set Table is only a temporary staging areabefore transformation occurs.
(B) A table that determines relationships – Incorrect
Relationship tables(e.g.,cmdb_rel_ci) definedependencies between recordsbut are not used for data import.
Import Set Tables do not determine relationships between records.
(C) A staging area for imported records – Correct
Import Set Tables temporarily store incoming recordsbefore processing.
The data is transformed and mappedbefore being inserted into the final target table.
This ensuresdata integrity and consistency.
(D) A repository for Update Set information – Incorrect
Update Sets (sys_update_set) store changes to configurations, such as scripts, workflows, and UI policies.
Import Set Tables are used for data imports, not Update Sets.
Explanation of Each Option:
Always review data in the Import Set Table before applying transformationsto avoid incorrect data entry.
Use Transform Mapsto define field mappings between Import Set Tables and target tables.
Monitor Import Logs(sys_import_set_run) for errors or incomplete data.
Delete old Import Set dataperiodically to improve performance and avoid unnecessary storage usage.
Additional Notes & Best Practices:
ServiceNow Docs: Import Set Overview
https://docs.servicenow.com
ServiceNow Community: Best Practices for Import Set Management
https://community.servicenow.com
References from Certified System Administrator (CSA) Documentation:
