Reltio Connect

Hi, I'm facing issues with manual merge when auto-unmerge is enabled and configured to address manually merged records also. The moment I merge the records manually from the potential matches view, they immediately get auto-unmerged. Can anybody suggest a solution to this?

Configuration for auto-unmerge:

We are using the following L3 configuration:

For entity type Individual,

"unmerge": {
  "enabled": true,
  "retainManualMerges": false
}

Match Rules:

Auto match rule is configured as Exact First Name, Exact Last Name, ExactOrAllNull Email Address

Scenario:

I created two new Individual entities from the SFDC source and observed an unexpected automatic unmerge behaviour after performing a manual merge.

Steps Taken:

1. Created a new Individual entity (entity1) from the SFDC source.
2. Created another Individual entity (entity2), also from the SFDC source.
3. Both of them have the same first name & last name. One has an email address, the other one doesn't have it.
4. Manually merged the two entities (entity1, entity2) via the Reltio UI using the "POTENTIAL MATCHES" view.
5. After refreshing the tenant, the entities were automatically unmerged.

Hi Sobhan, 

What you're seeing is actually expected given your current un-merge configuration. With

"unmerge": {
  "enabled": true,
  "retainManualMerges": false
}

any merge-whether auto- or manual-that no longer meets your match rule will be immediately split back apart. In your case, after you manually merge the two records, the combined record fails the "ExactOrAllNull Email Address" rule (one side has an email, the other doesn't), so the auto-unmerge engine kicks in and undoes your manual merge.

To fix this I could propose the following options: 

1. Keep manual merges intact
   Change your config to preserve manual merges by setting retainManualMerges to true
2. Update your merge rule to be Exact First Name, Exact Last Name, ExactOrNull Email Address in this way you will not face this challenge when one of the profiles has email address and the other one does not; The ExactOrAllNull  means that both of the profiles do not have email address. 
   

   exactOrNull

   The comparison on the attribute is considered true if:

   • Both attributes have values AND pass the test for exact OR
   • One attribute has a value while the other does not OR
   • Both attributes have no values

   exactOrAllNull

   The comparison on the attribute is considered true if:

   • Both entities have values AND pass the test for exact OR
   • Both entities have no values

I am attaching relevant Reltio documentation: 

• Automatically Unmerge Entity Records 
• Enable automatic unmerge on tenant configuration 
• Comparison Operators

Best Regards, 

Hi Petya,

Thanks for the reply. I was expecting the auto-unmerge to trigger when a record is updated (after the merge). Could you please help me understand what the trigger point for auto-unmerge is? Is it triggering just because the OV is updated as a result of the merge?

Thanks and regards,
Sobhan

"unmerge": {  "enabled": true,  "retainManualMerges": false}

Hi Sobhan,

Great question!

When you merge two profiles in Reltio, the system actually fires off two events in quick succession:

1. ENTITY_MERGED - indicating that a merge operation has been requested.

2. ENTITY_CHANGED - because under the covers the merge writes out a brand-new, combined entity version (with updated operational values).

Auto‐unmerge in Reltio isn't waiting for a separate "profile update" after manual merge - the merge operation itself counts as an update, and that write immediately fires the unmerge evaluation. Because every write to an entity version (create, update, merge, delete) immediately triggers both the matching engine and the auto-unmerge engine

"unmerge": {  "enabled": true,  "retainManualMerges": false}