IRE - Prevent Records with an Older Last Discovered Date from updating CIs

[s4scott]

Scenario: Sources for Thin Client data and SCCM data, both with Service Graph Connectors are updating computer records. When a Windows client is converted to a Thin client IRE will allow the older SCCM record with an older Last Discovered Date to update the newer data for that CI from the Thin Client SGC.

I found the system property: glide.identification_engine.skip_updating_source_last_discovered_if_older 
But it only prevents the update of the Last Discovered Date and Discovery Source fields.

I know preventing updates can be done in the logic of the SGC, but is this possible in IRE? 

[Pratiksha]

is it updating wrong record? If no then that's normal behavior if a match is found. 

[s4scott]

Identification is correct, the data is being written to the expected record. The hope is that there would be a way to prevent older/stale data from a source from overwriting newer data when both sources have the same priority in the Reconciliation rule set. 
The alternative is to build this logic into all of the sources individually. If it were only two sources, as in my example this wouldn't be a big deal, but there are dozens that will need to be updated.

[CasperJT]

Hi Scott,

Have you tried using Reconciliation rules? This should enable you to define which Discovery sources to prioritize and you can define which attributes each source is allowed to update.

Additionally you can set data refresh rules that define how old data should be from your primary source before moving on to the next:

This is all done in the CI Class Manager.

I hope this helps.

//Casper