Why identification rule is considering 2 CIs with same name and different SerialNumbers as duplicate

[sainathsand]

Hi,

We have implemented an integration using Integration hub ETL which transforms the data into custom CI table(cmdb_ci_monitor) which is a child of cmdb_ci_hardware.

Source data consists of multiple CIs with same name, but serial number of those CIs are different. We use Serial Number as source native key.

When we ran the integration, it was noticed that CIs with same name are being treated as duplicates by identification rule even though the CIs have different serial numbers.

Example payload:
1) "name": "Test 01 (monitor)",
"serial_number": "10CVU855"
2) "name": "Test 01 (monitor)",
"serial_number": "10CVU867"

Ran Identification simulation and logs have this error: 
1 : 2025-06-26 07:55:22 : Info : identification_engine : logId:[dc0e89ba2c96] DUPLICATE_PAYLOAD_RECORDS Found duplicate items in the payload (index 0 and 1), using className [cmdb_ci_hardware] and fields [name]. Remove duplicate items from the payload
2 : 2025-06-26 07:55:22 : Info : identification_engine : logId:[dc0e89ba2c96] DUPLICATE_PAYLOAD_RECORDS Found duplicate items in the payload (index 1 and 0), using className [cmdb_ci_hardware] and fields [name]. Remove duplicate items from the payload

Identification rule on cmdb_ci_hardware is applied here, and serial number attribute is given the most priority(100) compared to name(priority 200). But why it is considering the payload as duplicate when serial numbers are different.
Note: There are no identification rules set up on cmdb_ci_monitor, so IRE is following parent rule(cmdb_ci_hardware).

[Mark Manders]

It will run through both. But why not add rules for 'monitor' so it will skip the 'hardware' ones and just checks the specific table? If name is on the hardware table, you will run into risks here.

[Sandeep90]

@sainathsand IRE deduplicates the payload using the identification rules before checking the IRE rules, in your case if name is not unique, i recommend to override the rules at cmdb_ci_monitor and remove the name rule.