I wanto to know the meening of these fields.

[t-takumi]

I would like a detailed explanation of the meanings of the skipped and processed fields in the conversion history table [sys_import_set_run].

I checked the official product documentation, but it didn't mention this table.
https://www.servicenow.com/docs/r/ja-JP/zurich/integrate-applications/system-import-sets/t_CreateATr... 

[Nilesh Pol · Accepted solution]

hi @t-takumi 

In ServiceNow, the "sys_import_set_run" table is used to track the execution of import set runs. When data is imported into ServiceNow using an import set, the system logs the details of the import process in this table. Two important fields in the conversion history table are Skipped and Processed, and they provide insights into the status of the records during the import process. Here's a detailed explanation of these fields:

The "Skipped" field indicates the number of records in the import set that were ignored or not processed during the transformation process.

Possible Reasons for Skipping:

No Matching Transform Map: If no transform map is configured to process the imported data, the records will be skipped.
Filter Conditions in the Transform Map: If the transform map has conditions that exclude certain records, those records will be skipped.
Duplicate Records: If duplicate detection is enabled and a record is identified as a duplicate, it may be skipped.
Errors in Data: Records with invalid or incomplete data that do not meet the requirements of the transform map or target table may be skipped.
Inactive Transform Map: If the transform map is inactive, the system will skip processing the records.

The "Processed" field indicates the number of records in the import set that were successfully processed during the transformation process.

What It Includes:

Records that were successfully inserted into the target table.
Records that were successfully updated in the target table (if the transform map is configured to update existing records).
Records that were successfully ignored due to specific transform map rules (e.g., "Ignore" rule in the transform script).

Processed vs. Skipped:

Processed records are those that the system actively worked on, whether by inserting, updating, or applying other transformation logic.
Skipped records are those that the system did not attempt to process due to specific conditions or errors.

How Are These Fields Populated?
During the execution of an import set, the system evaluates each record in the import set table against the transform map(s).
Based on the outcome of the evaluation, the system increments the appropriate counters:
If a record is successfully transformed and processed, the "Processed" counter is incremented.
If a record is ignored or excluded from processing, the "Skipped" counter is incremented.

Example
Suppose you import 100 records into an import set table, and the following happens:

80 records are successfully inserted or updated in the target table.
10 records are identified as duplicates and skipped.
10 records have invalid data and are skipped.
In this case:

Processed = 80
Skipped = 20

[Mark Manders]

What exactly do you want to know? It simply states what is processed and what isn't.

[Tanushree Maiti]

Hi @t-takumi 

Processed: The total count of import set rows that were successfully executed by the transformation process.

                       Here total count = records for insert + records for update

Skipped:  If there is no fields updated, so the update was skipped/ignored. Skipped usually indicates a system-level decision based on configuration (like coalesce), whereas Ignored may refer to a script-driven decision

• Reasons for Skipping:
  • Missing Coalesce Values: the input data was skipped (similar to ignored) due to missing coalesce values.
  • No Field Differences: The incoming data is exactly the same as the data currently in the target record, resulting in no changes.