CI Identifier on Computers doesn't seem to work when loading via SCCM Service Graph Connector

[Abilash Vangara]

Hello, 

I'm trying to load computers via SCCM Service Graph Connector I see some weird behavior not sure if CI Identifiers expected to work like this

The identifier attributes on hardware (parent of computer - cmdb_ci_computer) table is as follows (by priority in the same sequence)

1. Correlation Id - Hardware table

2. Product Instance identifier - Hardware table

3. Serial Number, Serial Number Type - Serial Number table

4. Serial Number - Hardware table

5. Name - Hardware table

6. Mac Address, Name - Network Adapter table

There is a difference of records(1000 out 40K total) of in source data vs target data. Every CI loaded from source (SCCM) has correlation id however it doesn't seem to match with correlation id, perhaps matching with Serial Number.

During transform it runs by CI identifiers by priority to see if a match is found with correlation id (since correlation id is on every record loaded form source) if no match found or in case correlation id is loaded as empty then it jumps to next priority attribute - is my understanding correct?

- If correlation id column is loaded empty does the system try to match empty correlation id record in target table and update it?

- I want to understand under what exact circumstances it tries to find a match with next priority attribute in CI Identifier list - all scenarios?

- Does it matter when a CI record already exist which initially matched with serial number and now we started adding Correlation id in the new load?

- I believe only when none of the attribute (of all priorities in the list) match a new Ci is inserted?

Any help is greatly appreciated

Thank you

- Abilash