No more Duplicate CIs please

[Henrik Jutterst]

I'm looking for a way to stop creating Duplicate records of a CI based on rules in IRE.

I've created duplicate CIs with the same name in the Windows class.


I was hoping to find a setting so that I get a error message from IRE if there is a duplicate CI that is beeing inserted or updated, but I'm not sure if there is such a setting?

 

CMDB View says this:
20 Windows Servers that are duplicates.

The settings I have switched back and forward are these:

 

So, tell me - is there a setting for preventing a user/integration to submitting duplicates and what does it look like?

Here's a toping regarding this: https://community.servicenow.com/community?id=community_blog&sys_id=3efc66a5dbd0dbc01dcaf3231f96193b

Looking at this post it says:
"When duplicates are detected, the CI payload still may or may not be written to a record in the CMDB.   This depends on the system property named glide.identification_engine.skip_duplicates.   This is an internal system property in the sys_properties table.   By default, the skip_duplicates property is set to true (default value).   This means that if duplicate CIs are detected by the IdentificationEngineScriptableApi function, the CI payload will overwrite the oldest duplicate CI.   That is the CI with the oldest date/time in the updated field.   If skip_duplicates is set to false, then the CI is rejected and none of its fields are written to the CMDB."

Nope. Not getting that result when adding a new CI after a new CI..

[Henrik Jutterst]

Maybe something that @vNickNOW have an idea of how to fix? 🙂

[bammar]

I havnt been in this space in a while but i remember there being Normalization built into discover- not sure how much configuration is possible. If all else fails perhaps a BR on insert that does some checks and aborts if it matches based on what you deem to be a definite duplicate

[Henrik Jutterst]

I hear you and yes, that's sort of the last step...

But I really want to use the IRE in this case since it's a part of the platform and the place where we define all identification rules for each and every class in the CMDB.

But thanks for the input though!

[Michael de Boer · Accepted solution]

Did you created the CIs manually?
I think IRE doesn't apply on a manual insert.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0750386

Or did you used an import set?
In that case, did you add a transform map script?
https://docs.servicenow.com/bundle/sandiego-servicenow-platform/page/product/configuration-managemen...

Regards,

Michael