Identification and Reconciliation rules versus Coalesce

[Wawrzek]

Hi All,

I am trying to understand if CI Identification and Reconciliation when used for update sets will disable\overrule the coalesce field set in the transform map. I found this article stating that I&R can be turned by using script https://docs.servicenow.com/bundle/newyork-servicenow-platform/page/product/configuration-management...

but it does not explain what happens in such case with existing coalesce setup?

In SCCM HI knowledge base https://hi.service-now.com/kb_view.do?sysparm_article=KB0748948 which is a specif case and might not apply in general it is said that:

 The sequence of scripts being evaluated during a transform is as follows:

• source script for (coalesce) field(s)
• onBefore script
• script for transform map

Which suggested that maybe both options can coexist meaning first coalesce is checked and if not found then script using I&R will be used?

Ideally I imagine that in import set upload a CI unique identifier is used (set in coalesce) but if not matched the identification rules based on name and SN (for example) jump in...

Can someone clarify this for me?

Thanks in advance.

[Daniel Borkowi1]

Hi,

I would recommend not to mix both. Regarding populating CMDB use the R and I Engine like described in https://docs.servicenow.com/bundle/newyork-servicenow-platform/page/product/configuration-management.... Define no coalesce field in transform map. the Identification ensures, that the right CI will be selected to update. An additional coalesce can only lead to duplicates.

Greets

Daniel

[Daniel Borkowi1]

Found in a Training for CMDB:

"The IRE performs identification of each source record before it is inserted into the CMDB. The IRE determines if the record is a new CI or an already existing CI in the CMDB. 

• If new: insert the record to the target table
• If not new: update the existing CI in the CMDB, with data from the source record

To accomplish this, an onBefore script must be configured as part of the transform map which needs to call the CMDBTransformUtil API. The CMDBTransformUtil API pre-processes the source data and then passes the input values from the import set to the IRE. When the CMDBTransformUtil API is called during the import process, any coalesce values set in the transform map are ignored." [Source Now Learning Configure the CMDB]

[Wawrzek]

Hi Daniel - thanks this answers perfectly my question.