---
sourceDocument: Australia Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Robust import set transformer properties

# Robust import set transformer properties {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 Robust import set transformer properties

The Robust Import Set Transformer properties in ServiceNow define the rules and restrictions for updating Configuration Items (CIs) during import set processing.
These properties control how the Import Reconciliation Engine (IRE) handles CI reclassification and updates, ensuring data integrity and preventing unintended changes such as downgrades, upgrades, or class switches.
Show full answer Show less  
These settings are configured at the IRE payload level via the Robust Import Set Transformers form (System Import Sets \> Administration \> Robust Import Set Transformers). Properties set here apply globally to all rows in an import unless overridden at the individual item level through IntegrationHub ETL, which takes precedence.

## Key Features

* **Update Restrictions:** Control whether updates can occur without permitting downgrades, upgrades, or class switching, helping maintain CI classification consistency.
* **Class Reclassification Controls:** Manage whether CI classes can be downgraded, upgraded, or switched to a different branch in the hierarchy, which affects attribute sets of the CI.
* **Identification Priority:** The `ire.skipsysobjectsourcematching` property determines whether IRE identification rules take precedence over sysobjectsource lookup for uniquely identifying CIs. Setting this to true helps avoid duplicates when source attributes change but the native source key remains the same.

## Practical Use and Impact

By configuring these properties, ServiceNow customers can:

* Enforce strict update policies to prevent unintended CI downgrades or upgrades during imports.
* Control how CIs are reclassified in the CMDB, maintaining data quality and classification accuracy.
* Optimize CI identification during import reconciliation to reduce duplicate records, especially when identifier attributes fluctuate.

These controls are critical for maintaining a reliable and accurate CMDB when importing large datasets and managing CI lifecycle changes.  
Properties that define the types of updates that are permitted.

## Properties for CI reclassification {#robust-import-set-xform-props__section_ccb_fxv_hrb}

To configure properties, navigate to System Import SetsAdministrationRobust Import Set Transformers.

The properties defined in the Robust Import Set Transformers form are at the IRE payload
level and apply to all rows for the given import. If you define properties at the individual
item level using IntegrationHub ETL, they take priority over properties defined at the IRE
payload level. For more details about CI reclassification, see, [CI reclassification during IRE
processing](https://www.servicenow.com/docs/access?context=c_CIReclassification&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US).
{#robust-import-set-xform-props__table_t2x_kth_krb__entry__3}

| Name | Value | Description |
|-|-|-|
| ire.input.items.settings.updateWithoutDowngrade | true/false | Valid values: * true: Update the item but don't permit a downgrade. * false: Update the item and permit a downgrade. {#robust-import-set-xform-props__ul_tjn_nth_krb} Default: false |
| ire.input.items.settings.updateWithoutUpgrade | true/false | Valid values: * true: Update the item but don't permit an upgrade. * false: Update the item and permit an upgrade. {#robust-import-set-xform-props__ul_bkn_nth_krb} Default: false |
| ire.input.items.settings.updateWithoutSwitch | true/false | Valid values: * true: Update the item but don't permit class switching. * false: Update the item and permit class switching. {#robust-import-set-xform-props__ul_ocv_4th_krb} Default: false |
| ire.input.items.classDowngrade | true/false | Valid values: * true: Update the CI class to a class that is higher in the class hierarchy, and the newly assigned class is a parent of the current class. * false: Update the item but don't permit a class downgrade. {#robust-import-set-xform-props__ul_vcv_4th_krb} Default: false |
| ire.input.items.classUpgrade | true/false | Valid values: * true: Update the CI class to a class that is higher in the class hierarchy, and the newly assigned class is a parent of the current class. * false: Update the item but do permit a class downgrade. {#robust-import-set-xform-props__ul_n2d_qth_krb} Default: false |
| ire.input.items.classSwitch | true/false | Valid values: * true: Update the attribute. The newly assigned class is in a different branch in the class hierarchy and has a different set of attributes than the current class. * false: Update the attributes but don't permit a class switch. {#robust-import-set-xform-props__ul_w2d_qth_krb} Default: false |
| ire.skip_sys_object_source_matching | true/false | Determines whether IRE identification processes have the priority in being used to uniquely identify CIs in a payload, over the use of sys_object_source lookup. When set to true, the system prioritizes sending any payload that contains a criterion attribute to be processed by IRE identification instead of using sys_object_source lookup. This can be useful in situation that can potentially generate duplicate CIs. For example, using sources in which identifying attributes are changing while the source native key isn't. However, when source_native_key is the only identifiable attribute (for example, if none of the identification rules can run because attributes and values for rule identifiers aren't present in the payload), then source_native_key is used for identification even when the property is set to true. * Type: true \| false * Default: false * Learn more: * Location: [Add to System Properties \[sys_properties\]](https://www.servicenow.com/docs/access?context=t_AddAPropertyUsingSysPropsList&version=australia&pubname=australia-platform-administration&ft:locale=en-US) table. {#robust-import-set-xform-props__ul_nm3_gqz_v2c} |
[Table 1. CI reclassification properties]

{#robust-import-set-xform-props__table_t2x_kth_krb}

*[\>]: and then