Does "Create CI on insert" business rule prevent duplicate record insert in asset management?

[Flybook]

Hello experts!

Does "Create CI on insert" business rule prevents duplicate inserts?

We have this BR enabled, but still when we try manual and Insert and Stay record creation, the system is NOT prevent from creating duplicates for any process.

Any idea why?

If we create transform map for asset insert, do we need to coalesce serial number (or any other) field to prevent duplicate insert? 

According to below playbook, it should but it does not. Please provide input. 
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0999333

Thank you!

[Ed Laar]

Hi Flybook,

Create CI on Asset inserts creates a CI in the CMDB as soon as an Asset is created in the AMDB. There is also a BRules doing this in the opposite way. These BRules assure a correct 'relation' between Assets and CI's.

Preventing from duplicates is an other topic. On Asset insert a simple check should be done if for example the Asset tag of the new CI is unique in the AMDB. On CI insert a check should be done is the serial number - Model combination is unique. Note that there are more ways to check on duplicate records. In my mind this is highly configurable on the CI side (CI Class manager) but less or perhaps not OOB configurable on the Asset side.

Last but not least and perhaps the hardest part: Assume that on both sides the prevent duplicate records functionality is configured. It still can be the case that although the Asset is unique (as the Asset tag is unique for example) the related CI creation is refused due to the configured prevent duplicate capabilities on CI side. How to deal when this occurs? This scenario can also happen on Asset insert after CI insert.

I have not the direct answer for this. Perhaps somebody else??

Ed

[Mahendra RC · Accepted solution]

Hello Flybook,

The Create CI on Asset insert creates a CI in the CMDB when the Asset is created in the Hardware table. The BR will not restrict the Duplicate CI from getting created. If you try to create a duplicate Asset manually then the BR will not do any check for duplicate CI. Hence you will be able to create duplicate Asset creates and also duplicate CIs will be created.

However if you have CI with Serial Number SERIALHP001 in CMDB but somehow you don't have the corresponding Asset record in AMDB with Serial Number as SERIALHP001 then if you try to create an Asset with SERIALHP001 as serial number then it will not allow you to create the Asset and you will get errro stating something like "There is already a CI existing with same serial number: SERIALHP001.

But it will not restrict you from creating duplicate Assets.

Please mark my response as helpful/correct, if it answer your question.

Thanks

[Flybook]

Thank you for your response Mahendra,

Activating this BR in dev did work to populate CI name with serial number and model name but it didn't work in Test environment. 

Can you give an inside of what may be causing this issue?

Thank you!

[karinmolly]

Thanks a lot for this conversation. I love servicenow.com this resource I am glad to be part of community.