Import set - Unable to resolve target record, coalesce values not present

[luigistracc]

Hello there,

I need some help troubleshooting my data import.

The import set shows that the data is loaded correctly :



But when I run the transform map, all records are ignored and return the error “Unable to resolve target record, coalesce values not present: u_inventory_number.” and it runs endlessly if I do not cancel it manually. 


Here is the transform map and field map :



I've seen on similar post that import_attribute_name needs to be different than Column name, is it still true ?
Here's the dictionary entry for u_inventory_number

Additionally, we have multiple similar Data Sources (for OS version, CIs, etc...) that work perfectly fine but every data source that deals with IPv4 does not work.

Do you have any idea what might be the issue?
Thanks a lot. Any help appreciated!

[AnirudhKumar]

I see you are trying to do an manual import into the CMDB. In this scenario do not rely on Coalesce. The best practice is to make use the IRE during the import.

Refer to below documentation:

https://www.servicenow.com/docs/r/servicenow-platform/configuration-management-database-cmdb/identif...

Basically you will turn off coalesce on your field mappings and write an onBefore transform script containing the script in that documentation. Ensure you have Identification Rules and Entries in place for your CI class.

Also, on seeing your error now I think there are no values in your import set table for the field u_numero_dinventaire.
You have a coalesce on this field, and ServiceNow is trying to look for those values against u_inventory_number field in your IP Network table. If the value is empty, ServiceNow has nothing to compare against. 

Edit1: Added what additionally needs to be done in IRE

Edit2: Follow up question

[Tanushree Maiti]

Hi @luigistracc 

Please confirm  that your source data has no empty or null values in the u_inventory_number field, which is set as a coalesce field in the transform map.

The endless running could be the case that the system is repeatedly attempting to process the problematic record(s).