Importing Ci data through Excel without going through the Identification Rule and Reconciliation Rules, resulting in duplicate imported data

[Peter64]

Importing Ci data through Excel without going through the Identification Rule and Reconciliation Rules, resulting in duplicate imported data? ? ?

[#2]

It is difficult to answer your question without any examples.  Indentification rules are complicated and will match if any of the rules result in the same identification.  For instance, name can be troublesome.  You could have 2 CIs with the same name but different serial numbers.  Logically you may think that because there is an IRE rule on serial number it would say the 2 are not the same CI.  Unfortunately it will agree they are not the same CI by serial number but then get to the name rule and identify them as a match.

Without any further information you likely won't find a lot of insightful help.  I would encourage you to post examples of the CIs that are duplicates and screenshots of the IRE rules for those CI classes.

[VivekSattanatha]

Hi,

If you are importing data then always Identification and reconciliation so that later when you do discovery or through other source integration the record wont get duplicated.

Regards,

Vivek

[Mark Bodman · Accepted solution]

The XLS import process in the User Experience on List views doesn't use IRE or Multi-source rules.  I wouldn't recommend using that process for CI's.  Instead, I would leverage IH-ETL to import this data, where IRE, Multi-source rules can be applied to help avoid duplicates and to facilitate merging data from many sources into the same records.

Additionally, you can leverage Service Graph connectors in the store, which are built using IH-ETL to ingest data from known 3rd party sources.  XLS isn't one that we cover however, and generally not a great source for ongoing ingestion processes into the CMDB.

[VaranAwesomenow]

https://www.youtube.com/watch?v=5Ktqav2YUUI a demo of loading data to cmdb using ETL.