Duplicate assets creation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-01-2024 10:26 AM
Hi All,
I have duplicate assets created although if assets are having same serial number ,same model ,same model category.
Could you please help me to understand what is causing to create duplicate assets .
if asset was already there with same attribute values then if CI was created that CIs not mapped to already created asset.CI is inserting another asset .
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-02-2024 08:43 AM
Hi @_bhishek,
Thanks for the extra details.
I'm racking my brain as I experienced something similar some years ago when integrating SCCM.
From memory, it was caused by a Business Rule on the CI table.
Based on the event flow you've explained, you may be experiencing the same issue and cause.
The CI table has a Business Rule called: 'Create Asset on insert' (Active on the baseline configuration)
Despite there already being a matching Asset on the Asset table (based on serial number etc), the logic is triggered and based on the newly created CI. If the CI does not have an associated Asset, this Business Rule will create one - hence the duplicate.
To test this theory, on your Dev environment, can you disable this Business Rule and confirm whether you're seeing the duplicate being created please?
If this is the culprit, you'll have to update the Business Rule accordingly - either check for existing records via this BR, or inactivate it.
To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Helpful.
Thanks, Robbie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-05-2024 05:49 AM - edited 02-08-2024 01:49 AM
Hi @_bhishek,
Did you see my latest response?
I believe it is the CI table Business Rule called: 'Create Asset on insert' (Active on the baseline configuration)
Despite there already being a matching Asset on the Asset table (based on serial number etc), the logic is triggered and based on the newly created CI. If the CI does not have an associated Asset, this Business Rule will create one - hence the duplicate.
To test this theory, on your Dev environment, can you disable this Business Rule and confirm whether you're seeing the duplicate being created please?
If this is the culprit, you'll have to update the Business Rule accordingly - either check for existing records via this BR, or inactivate it.
@_bhishek - To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Helpful.
Thanks, Robbie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-02-2024 02:54 AM
If the assets are created from CIs, check the identification rules of the respective CI classes (like cmdb_ci_computer). To do this, go to CI class manager and open the required CI class. Then click on 'identification rules' tab. Check whether the identifier entries need to be updated.
Also note that if manual data imports of CIs are done without using 'integration hub ETL', the identification rules won't be considered and there is a possibility of duplicates getting created even when the identification rules are properly defined. Same situation can happen in the case of 3rd party integrations which populate the CMDB without using service graph connectors.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-13-2024 09:38 AM
Thanks for response. In my case ,There is a OOB Asset and CI script include and we customized this .So Asset creation was not creating CI as OOB updates were not being captured .We have reverted to latest vesrion.Now we are creating CI for each asset .So when same serial number CI is inserted so same CI and asset is updated .NO duplicate asset is being created.