De-Duplicating Hardware Models

[Jbelter]

What has been other peoples solutions to de-duplicating Hardware Models? I was looking at this KB article:
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0999448
But the issue I see with this is - it is a one-time fix (unless I am missing something). This won't work for models that are created multisource CMDB. Data sources will bring in CI data (which normally includes the model) on a schedule (usually weekly/daily).

In these cases the original duplicate hardware model will just be recreated (or at least this is what I have seen in my experience).

My current solutions uses a script include that is called from a business rule that triggers on insert/update of the cmdb_hardware_product_model table. This way whenever a new model is created, it is de-duplicated against already existing models.

Have you guys experienced duplicate Hardware Model issues, and if so how did you solve them?

[Sumanth16]

Hi @Jbelter ,

I didn't work on De-Duplication but below are the community articles which are used different methods for avoiding duplication:

https://www.servicenow.com/community/developer-forum/remove-multiple-duplicate-model-script-help/td-...

If I could help you with your Query then, please hit the Thumb Icon and mark it as Correct !!

Thanks & Regards,

Sumanth Meda

[Lithesh · Accepted solution]

Hi @Jbelter,
From My point of view, I have faced this issue with the creation of multiple duplicate models because of multiple discovery sources. So what I did is the same as you I have configured the Business rule in the Model table so that before any new model record is created. It will check if the model is already available or not. If it's available, it won't create. If not, It will create a new model. To remediate the existing duplicates. I have configured a flow with a custom action where it will automatically find the duplicates and authenticated model against the duplicate and re associate them.

Thanks,
Lithesh

[ndube82]

We have the same/similar problem.  It is silly.  OOB the system should prevent these duplication issues especially when it comes to discovery created models.  My biggest issue is the lack of attribute population when models are created.  They can't be normalized most times which renders the Content Library not trustworthy.  This needs attention and solution by the provider!

[Lithesh]

@ndube82 

Yes, This needs to be addressed by the ServiceNow. But the thing as per ServiceNow standard if there are two models with same model number then it is considered as duplicate. Here the thing is not all models is populated with the model number since the discovery source does not have those data for some models. That's why they did not have any restrictions it seems.

Regards,
Lithesh