---
sourceDocument: Brazil ServiceNow AI Platform Capabilities
sourceDocumentLink: https://www.servicenow.com/docs/r/servicenow-platform

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Apply IRE to Import Sets

# Applying IRE to Import Sets {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Applying IRE to Import Sets

ServiceNow enables you to apply the CMDB Identification and Reconciliation Engine (IRE) processes to Import Sets when importing Configuration Items (CIs) into the CMDB.
This capability helps prevent the creation of duplicate CIs, which can occur when multiple identical records are imported.
By integrating IRE with Import Sets, you ensure that each record is either inserted as a new CI or reconciled with an existing one, maintaining CMDB integrity.
Show full answer Show less  

## Key Features

* **Transform Map Script Integration:** Use the `CMDBTransformUtil` API in the onBefore transform map script to invoke the identification and reconciliation process for each import set row. The script includes error handling and logging for traceability.
* **Duplicate Handling:** IRE checks each source record before insertion. If the record is a duplicate, it updates the existing CI instead of creating a new one. If not, it inserts the new record.
* **Multiple Target Tables:** You can specify different target CMDB tables per record within an import set by adding a target table column in the data source and mapping it in the transform map. This allows importing heterogeneous CI classes like Computer and Server in a single import set.
* **API Capabilities:** The `CMDBTransformUtil` API supports reference fields and source scripts to determine target values dynamically, enhancing flexibility in data transformation.

## Practical Implementation Details

* Add the call to `CMDBTransformUtil.identifyAndReconcile()` in the onBefore transform map script to apply IRE logic.
* Use `ignore = true;` in the script to prevent Import Sets from creating duplicate records after IRE has processed them.
* To direct records to different CMDB classes, add a target table column to the import data source, map this column's values to the `Class` field in the transform map, and do not rely on the default target table setting.

## Restrictions and Considerations

* Each import set should be associated with a single transform map even when using the CMDBTransformUtil API.
* The API does not validate mandatory fields; import failures occur if mandatory fields are missing regardless of transform map settings.
* IRE cannot be applied to Import Sets for dependent CIs that use dependent identification rules.

## Benefits for ServiceNow Customers

By applying IRE to Import Sets, you can reliably import CIs into your CMDB without creating duplicates, ensuring data accuracy and consistency. The ability to handle multiple target tables in a single import streamlines data integration for diverse CI classes. Using the provided scripting approach and API ensures that you maintain control over data reconciliation during import, reducing manual cleanup efforts and improving CMDB quality.  
You can apply CMDB Identification and Reconciliation Engine (IRE) processes when Import Sets are used to import CIs into the CMDB. CI identification can prevent duplicate CIs in the CMDB, which Import Sets might otherwise
cause.
Populating CMDB tables using Import Sets can inadvertently result in duplicate CIs when
multiple imported records are identical to an existing CI. To minimize this duplication, you can
apply CMDB Identification and Reconciliation processes to Import Sets when importing new
records into CMDB tables.

## Transform map script {#identification-import-sets__section_bjc_x5t_p2b}

In the onBefore transform map script for an import set, add a call to the [CMDBTransformUtil](https://www.servicenow.com/docs/access?context=c_CMDBTransformUtilAPI&version=brazil&pubname=brazil-api-reference&ft:locale=en-US) API, similar to the following code sample:

    (function runTransformScript(source, map, log, target) {
    // Call CMDB API to do Identification and Reconciliation of current row
    var cmdbUtil = new CMDBTransformUtil();
    cmdbUtil.setDataSource('ImportSet');
    cmdbUtil.identifyAndReconcile(source, map, log);
    ignore = true;

    if (cmdbUtil.hasError()) {
            var errorMessage = cmdbUtil.getError();
            log.error(errorMessage);
    } else {
            log.info('IE Output Payload: ' + cmdbUtil.getOutputPayload());
            log.info('Imported CI: ' + cmdbUtil.getOutputRecordSysId());
    }

    })(source, map, log, target);

The `ignore = true` code phrase prevents Import Sets from creating the same
record again after it is processed by the identification engine.

## Process {#identification-import-sets__section_y3h_z5t_p2b}

The identification engine performs identification of each source record before it is inserted into the CMDB. The identification engine determines if the record is a duplicate of an existing CI, and then:

* If not duplicate: Inserts the record to the target table.
* If duplicate: Updates the existing CI in the CMDB, with data from the source record.
{#identification-import-sets__ul_uvf_ddh_sbb}

The CMDBTransformUtil API pre-processes the source data, then passes the input values to the
identification engine with import set being the data source by default. The CMDBTransformUtil
API supports a target field that is a reference field in the same manner that Import Sets
supports it. The CMDBTransformUtil API also supports a source script, evaluating source scripts
to determine the target value which is then passed to the identification engine. For more
information, see [Creating a field map](https://www.servicenow.com/docs/access?context=t_CreatingAFieldMap&version=brazil&pubname=brazil-integrate-applications&ft:locale=en-US).

## Specify multiple target tables for an import set {#identification-import-sets__section_d1k_mpk_thb}

You can configure each record in an import set with its own target table. Then, instead of
inserting all the transformed records into a single target table, the records are inserted into
the different target tables that are specified per record. For example, you might need to insert
some records from the import set to the Computer class and other records to the Server
class.  
When [importing data using Import Sets](https://www.servicenow.com/docs/access?context=c_ImportDataUsingImportSets&version=brazil&pubname=brazil-integrate-applications&ft:locale=en-US), incorporate the following steps:

* In the data source file, add a target table column. Use a string such as "MyTable" to label the column header. In each record row, enter the target table for the record, as a valid CMDB class name such as "cmdb_ci_computer".
* After you Auto Map Matching Fields on the Table Transform Map form, add a field map for the added target table column to establish a relationship between classes and the target tables in the CMDB.
  1. In the Field Map related list on the Table Transform Map form, click New.
  2. Set Source field to the header of the target table column that you added in the data source file, such as <kbd class="ph userinput">MyTable</kbd>.
  3. Set Target field to Class.
  4. Click Submit.
  {#identification-import-sets__ol_tnq_nyk_thb}
{#identification-import-sets__ul_lqt_g4r_thb}

When you configure an import set with multiple target tables as described in the steps above,
the Target table that is specified on the Table Transform Map form is not
used.

## Restrictions {#identification-import-sets__section_fxs_xyt_p2b}

The following restrictions apply:

* An import set should be associated with a single transform map. While adding a call to the CMDBTransformUtil API, ensure that still a single transform map exists for the import set.
* The CMDBTransformUtil API does not check if mandatory fields have values when used with Import Sets . Regardless of how enforce mandatory fields is set in the transform map, data import fails if a mandatory field does not have a value.
* CI Identification and Reconciliation cannot be applied to Import Sets for dependent CIs (CIs with dependent identification rules).
{#identification-import-sets__ul_zfs_yyt_p2b}
**Related topics**   

* [Create a transform map](https://www.servicenow.com/docs/access?context=t_CreateATransformMap&version=brazil&pubname=brazil-integrate-applications&ft:locale=en-US)