Import set transform error: mapping failed for row

Transform map script contains JavaScript errors or references undefined variables, causing the transformation to fail during execution. (high likelihood)

Field mapping attempts to write invalid data types or values that violate target table field constraints, such as inserting text into integer fields. (high likelihood)

Required fields in the target table are not mapped or contain null/empty values when the transformation attempts to create records. (medium likelihood)

Reference field mappings point to non-existent records or use invalid sys_ids, causing foreign key constraint violations. (medium likelihood)

Business rules or ACLs on the target table prevent the transformation from creating or updating records with the mapped data. (low likelihood)

Step 1: Navigate to System Import Sets > Administration > Import Sets and locate the failed import set table to identify the specific row that failed transformation.

Step 2: Open the Transform History related list on the import set record and review the error details and stack trace to understand what caused the mapping failure.

Step 3: Check the System Log at System Diagnostics > Log > Application Log for detailed JavaScript errors or constraint violations related to the transform map.

Step 4: Open the Transform Map record and review all field mappings to ensure source fields contain valid data types and formats expected by target fields.

Step 5: Test the transform map script in the Script Debugger by adding debug statements and running a single row transformation to isolate script errors.

Step 6: Verify that all required fields in the target table have corresponding mappings or default values configured in the transform map.

Step 7: For reference field mappings, confirm that the referenced records exist and the mapping uses correct display values or sys_ids.

Step 8: After fixing identified issues, mark the failed import set rows as Ready and re-run the transformation to verify the fixes work correctly.