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.

[Dhananjay Pawar]

Hi,

coalesce comes in picture at the time of importing data using import set. And if you are importing data through discovery then I and R comes in picture.

Thanks,

Dhananjay.

[Wawrzek]

Hi Pawar,

What you said is true but not complete and hence my initial question.

If you check the link https://docs.servicenow.com/bundle/newyork-servicenow-platform/page/product/configuration-management... the I&R can be used for import sets but I don't know if this turns of coalesce or not...

[adilrathore]

Good question. I dont see the documentation saying that coalasce will need to be turned off if you are using CMDBTransformUtil but I think IRE would run on top of coalasce settings.

[Daniel Borkowi1]

Hi,

regarding CMDB data please use the Identification engine for every data source. Also for Import Sets, here is a helpful Howto in the Product Documentation: https://docs.servicenow.com/bundle/orlando-servicenow-platform/page/product/configuration-management...

This is more powerful then coalesce fields. You can define more complex Identification Rules then you are able with coalesce field. E.g. first check if there is a CI in the target table with the same Serial Number, if not then check Name, if not then check IP-Address and Mac-Address combination. Also, these fields can be entries in a related List (e.g. IP-Address table). You also avoid Duplicates when you also run Discovery to populate the CMDB. Strongly using I and R for populating CMDB.

Greets,

Daniel