---
sourceDocument: Xanadu ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/platform-administration

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Automatic matching of display values

# Automatic matching of display values {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

During the import of XML records, the system attempts to match some reference field
display values to a local sys_id value.

If the system finds an existing record with a matching display value on the local instance, the
import uses the sys_id of the existing record rather than the sys_id of the imported
record.

For example, suppose you export an incident record that is assigned to the user John Smith. In
the exported XML file there is an entry such as:

    <incident>
    	...
    	<assigned_to display_value="John Smith">7712173d2ba80200c5244f74b4da159a</assigned_to>
    	...
    </incident>

This user already exists on the target instance but has a different sys_id value such as:

    <sys_user><name>John Smith</name>
    	...
    	<sys_id>18cab8de2be80200c5244f74b4da15f7</sys_id>
    	...
    </sys_user>

Since the display value matches an existing record, the system uses the local instance's
existing sys_id value for the reference field such as:

    <incident>
    	...
    	<assigned_to display_value="John Smith">18cab8de2be80200c5244f74b4da15f7</assigned_to>
    	...
    </incident>

The system can match display values for the following tables.

* User \[sys_user\]
* Group \[sys_user_group\]
* Role \[sys_user_role\]
* Group Roles \[sys_group_has_role\]
{#c_AutomaticMatchingOfDisplayValues__ul_ks1_gfk_3s}