IRE rules while setting up multiple discoveries

[kiran kumar m1]

I have SG-INTUNE setup avaible in my instance , and I am getting the discovery data as well from it , now what i did is I have created a reconcilition rule in which I have mentioned Sg-Tanium prioirty is 100 and SG-Intune priority is 200 on fields like name , version , installed on , assigned to in software installation table , 

and I have prepared a excel in which i have given discovery source as sg-tanium and I have provided a data that is already exisiting and pulled by sg-intune 

and I have imported that data to software installations table  and ran the deduplicate job

what i am expecting is the new data that i have imported should be set as true (because i have a reconcilition rule for the sg-tanium discovery source which i have manually kept in the excel ) and the existing same data pulled by Intune should be false 

but its not making the existing intune data false , if i try to import the record second time its making one of the imported record false and another newly imported record true by me 

Is this how it works or am i missing something ?

[Pranesh Lokhand]

Hello @kiran kumar m1 

Importing data with a discovery source tag doesn’t override existing records by itself. The reconciliation engine decides which source wins, and you need to run the reconciliation job for the rules to take effect.

Reconciliation is source‑driven, not import‑driven. If you import data twice, the engine treats them as competing sources, which is why you saw one record flip to false and the new one set to true.

Imported records must have the correct discovery_source value and be recognized as coming from that source. If you manually set SG‑Tanium in Excel, ServiceNow may not treat it as authoritative unless the source is properly configured in the Discovery Source table.

Verify that your reconciliation definition is active and scoped to the right CI class.

Confirm that SG‑Tanium and SG‑Intune are properly registered as discovery sources in ServiceNow.

Run the Reconciliation Engine job (not just deduplication) after importing.

Check the reconciliation logs to see why Intune records aren’t being flipped to false — often it’s because the reconciliation key doesn’t match exactly (e.g., whitespace, case sensitivity, or mismatched field values).

If this response helps, please mark it as Accept as Solution and Helpful.
Thanks & Regards,
Pranesh L.