Duplicate assets creation

[_bhishek]

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

[Robbie]

Hi @_bhishek,

Can you share how Assets are created, please? How do you ingest the Assets into ServiceNow (if it is indeed a feed)?

Typical examples are integrations and SCCM.

Based on how the Assets are ingested, we can then ensure we check for duplicate values (typically based on the serial number) and whether to create or update.

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

[_bhishek]

Hi @Ashok Sasidhara @Robbie 

Thanks for your response .

I am importing Assets through JDBC data source. I am importing Configuration item through 3rd party integration. When importing Configuration item through flexera ,Ci is syncing with newly created asset rather than already available asset.Although Assets serial numbers are same.

Could you please help me to why this happening ,What is the logic behind to sync assets with CIs .What are the attributes should be same to sync with CIs.

Thanks.

[Robbie]

Hi @_bhishek,

When importing the data, is the data loaded into a 'staging table'? I would assume (and hope) so - please confirm.

Are you aware of and do you leverage 'Transform Maps'? This functionality allows you to manipulate or transform the source data prior to creating the record on the desired table(s) - in your case the CI related tables.

Within the Transform Maps you would be checking on the assumed unique identifier for each CI, the serial number, and using this to decide to either insert a new record or update an existing record. 

You could also transform certain data as you see fit prior to importing the data.

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

[_bhishek]

Hi Robbie,

Yes data is loaded in staging table. We do use transform map to  map data and using serial number as coalesce field .

When importing configuration item through flexera, There is also serial number as coalesce field in transform maps.

So For example if first I am importing asset through JDBC data source(with transform map having serial number as coalesce field with other attributes).

Then we are importing configuration item through Flexera .It is inserting/updating configuration item and each configuration item creating respective assets .Rather than configuration items are not syncing with assets if same serial serial number asset already available in alm_hardware table.

Could you please help me to understand how sync works between assets and CIs .If assets is already imported in asset table and after that if we importing configuration item with same serial number .What could be the reason Configuration item is not synced with already available asset .Is there any other specific requirement to sync the CI with asset.

Thanks