CSA Batch 19|| Day 11 || Import Set - Transform Map

ServiceNow Import Set & Transform Map (Day 11) This session focused on importing data from Excel into ServiceNow using Import Sets and Transform Maps, which are essential for bulk data loading and updates. Key Concepts 1. Why Import Data? Creating users manually is time-consuming when dealing with hundreds of records. Instead of creating records one by one, ServiceNow allows bulk imports from Excel or external systems. 2. Use ServiceNow's Standard Template For importing user data: Open the target table (e.g., User table). Right-click → Import. Download the Excel template. Benefits: Standard field names No spelling mistakes Consistent across teams and customers Includes all available fields in the table 3. Data Source & Import Set Table When loading an Excel file: ServiceNow first loads data into an Import Set Table. This is a temporary staging table. It allows validation and review before data reaches the actual table. Example Excel → Import Set Table → Target Table 4. Transform Map A Transform Map connects: Source Table (Import Set) Destination Table (Actual ServiceNow table) Purpose: Defines how fields should map between tables. Example: Source User ID → Target User ID Source Email → Target Email 5. Field Mapping Two methods: Manual Mapping Map each field individually. Example: user_id → user_id first_name → first_name Mapping Assist Automatically maps matching fields and saves significant effort. 6. Running the Transform After creating mappings: Load data into Import Set. Run Transform Map. Data moves into the target table. Check Transform History and Import Logs for results. 7. Reusing Existing Import Sets If the Excel structure remains unchanged: Reuse the existing Import Set Table. Reuse the existing Transform Map. No need to recreate them every time. If new columns are added: Update the Transform Map accordingly. 8. Coalesce (Most Important Topic) Problem: When importing again, ServiceNow doesn't know whether to: Create a new record Update an existing record Solution: Use Coalesce on a unique field (e.g., User ID). Coalesce Logic If Match Found → Update If No Match → Insert New Record Example: User ID = ABCD already exists → Update record User ID = XYZ new → Create record 9. Common Import Errors Errors occur when: Duplicate User IDs are imported without Coalesce. Business Rules prevent updates. Restricted fields are modified. Example shown: Changing Identity Type from Machine to AI triggered a Business Rule error