{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":22214,"path":"integrate-applications/system-import-sets/import-run-details.md","title":"Import run details","bundle":null,"doc_type":null,"release":"australia","body":"\n# Import run details\n\nView detailed information about import set runs, individual rows in the import set, and import logs.\n\nThere are two ways to run or process an import set. The data displayed after the run varies slightly depending on which way you choose.\n\n- **Robust import set transformers**\n\n Separate the transform and processing functions, providing a more flexible alternative to transform maps. Robust import set transformers enable you to extract data from a source table into an intermediary data structure. You can transform the data as desired and then load that data to one or more target tables. Records are processed as batches to enhance performance. For more information, see [Robust Import Set Transformers](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/system-import-sets/robust-import-set-transformers.md).\n\n- **Transform maps**\n\n Legacy method to map data from an import set staging table to a single target table. Transform maps combine the transform and processing functions into a single process. Each time you run a transform map, the system must load data from the import set staging table, transform it, and then insert it into a single target table. You can define multiple table mappings with multiple transform maps. For more information, see [Transform maps](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/system-import-sets/c_CreatingNewTransformMaps.md).\n\n\nAfter running the import, you can view the import history by navigating to the Import Set record and checking the tabs below the Related Links section. They cover the import set runs, import set rows, and import log.\n\n## Import Set Runs\n\nThe **Import Set Runs** tab provides details about individual imports.\n\n\\[Omitted image \"import-set-runs.png\"\\] Alt text: An Import Set record showing the Import Set Runs tab.\n\nThe following table provides more details about the fields in the image.\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nStarted\n\n\n\nDate and time the import started. Given in the time zone of the logged-in user.\n\n
\n\nState\n\n\n\nState of the import. Options are:- Cancelled\n- Cancel requested\n- Complete\n- Complete with errors\n- Did not complete\n- Running\n\n
\n\nCompleted\n\n\n\nDate and time the import finished. Given in the time zone of the logged-in user.\n\n
\n\nRun time\n\n\n\nTotal amount of time the import required to run.\n\n
\n\nTotal\n\n\n\nTotal number of import set rows.\n\n For an import using a robust import set transformer, this field is the total number processed, ignored, skipped, and with errors.\n\n For an import using a transform map, this field is the total number inserted, updated, ignored, skipped, and with errors.\n\n
\n\nInserts\n\n\n\nNumber of records inserted.\n\n
\n\nUpdates\n\n\n\nNumber of records updated.\n\n
\n\nProcessed\n\n\n\nNumber of records processed.\n\n
\n\nIgnored\n\n\n\nNumber of records ignored.\n\n An ignored record is one the user has specified should be ignored during an import. For example, you can identify records to ignore with the **ignore** variable in an onBefore script. For more information, see [Create Extract Transform Load \\(ETL\\) definitions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/system-import-sets/create-etl-definitions.md).\n\n
\n\nSkipped\n\n\n\nNumber of records skipped.\n\n A skipped record is one that has been skipped by the system, due to an internal issue.\n\n
\n\nErrors\n\n\n\nNumber of errors encountered during the import.\n\n
\n\nTransform Map\n\n\n\nIf data is imported using a transform map, the associated map is shown here.\n\n
\n\nRobust Transformer\n\n\n\nIf data is imported using a robust import set transformer, the associated transformer is shown here.\n\n
## Import Set Rows\n\nThe **Import Set Rows** tab provides details about rows included in the import set run.\n\n\\[Omitted image \"import-set-rows.png\"\\] Alt text: An Import Set record showing the Import Set Rows tab.\n\nThe following table provides more details about the fields in the image.\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nCreated\n\n\n\nDate and time the import set row was created. Given in the time zone of the logged-in user.\n\n
\n\nRow\n\n\n\nNumber for the row. Numbering starts at zero.\n\n
\n\nState\n\n\n\nState of the row import.\n\n
\n\nTarget record\n\n\n\nRecord updated with the row.\n\n This field displays the target record only when the import is run with a transform map.\n\n For imports run with a robust import set transformer, you can view the target records by clicking the row record and checking the **Target record** field in the **Transform Target Rows** tab. For more information and an example, see the following section on Target records for robust import set transformers.\n\n
\n\nError\n\n\n\nDetails for any errors encountered during the row import.\n\n
\n\nComment\n\n\n\nComments from the transform script.\n\n
\n\nTransform Map\n\n\n\nIf data is imported using a transform map, the associated map is shown here.\n\n
## Target records for robust import set transformers\n\nFor imports using a robust import set transformer, you can view additional details by running the import in verbose mode. Verbose mode enables the following.\n\n- Greater detail in the import log. With verbose mode, the import log includes transform logs that show how transform operations are applied to records.\n- More information about each row's transform target rows. For each row in the **Import Set Rows** tab, clicking the row record opens the row in the import set table. In this view, you can see the transform target rows, import log, and import set row errors.\n\nThe **Transform Target Rows** tab displays the state, target record, import set run, and any error messages for each row. The first three fields are all links to the associated records, making it easier to find and track information for improved debugging. For more information on enabling verbose mode, see [Create a robust import set transformer](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/system-import-sets/create-robust-import-set-transformer.md).\n\n\\[Omitted image \"transform-target-rows.png\"\\] Alt text: A row record showing the Transform Target Rows tab.\n\nThe following table provides more details about the fields in the image.\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nState\n\n\n\nState of the transform target row. Options are:- Inserted\n- Updated\n- Error\n\n
\n\nTarget record\n\n\n\nRecord updated with the row.\n\n
\n\nImport set run\n\n\n\nImport Set record associated with the transform target row.\n\n
\n\nError message\n\n\n\nText describing any errors encountered by the transform target row.\n\n
## Import Log\n\nThe Import Log tab displays the logs for the import set. It shows when each log was created, its level, the log message, and the source of the log. For details, see [Import logs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/r_ImportLogs.md).\n\n"}}