Reltio Connect

Hi , 

 I have configured the matchfield URI for both Phone and Email in an entity,merged    different records  entities having different Phone and Email. 

They are working expected after merge in both entity and nested-attributes  but after merge Email field is coming with all values where it should have only one where   Phone number is working fine .

They both have same survivorship strategy as below :- 

Email MatchfieldURI:- 

Data :- 

The fall back for Email/EMail is LUD

Please let us know what can be missing here for which multiple fields are present for Email.

-------------------------------------------

Hi, 

Looking at the screenshot, it looks like the Email.Email survivorship strategy is not able to break the tie to survive just one value. What is the fallback strategy configured ? 

Hi , 

 I have configured the matchfield URI for both Phone and Email in an entity,merged    different records  entities having different Phone and Email. 

They are working expected after merge in both entity and nested-attributes  but after merge Email field is coming with all values where it should have only one where   Phone number is working fine .

They both have same survivorship strategy as below :- 

Email MatchfieldURI:- 

Data :- 

The fall back for Email/EMail is LUD

Please let us know what can be missing here for which multiple fields are present for Email.

The primary strategy  is Source System and fall back is LUD and these records created from the UI one by one .

Hi, 

Looking at the screenshot, it looks like the Email.Email survivorship strategy is not able to break the tie to survive just one value. What is the fallback strategy configured ? 

Hi , 

 I have configured the matchfield URI for both Phone and Email in an entity,merged    different records  entities having different Phone and Email. 

They are working expected after merge in both entity and nested-attributes  but after merge Email field is coming with all values where it should have only one where   Phone number is working fine .

They both have same survivorship strategy as below :- 

Email MatchfieldURI:- 

Data :- 

The fall back for Email/EMail is LUD

Please let us know what can be missing here for which multiple fields are present for Email.

Ok, so if you are adding the different emails from the Reltio UI, then it means it's being associated with the same Reltio crosswalk. Now, as both the emails are associated with the same crosswalk, LUD survivorship may not be able to break the tie. 

Can you check two things 

• Use options = showAppliedSurvivorshipRules in get entity API and verify what survivorship strategy is being applied for the Email. 
  
• Also, verify from the Get API response whether the singleAttributeUpdateDate for those two emails are available or not. If available, check if it's same or different. 

The primary strategy  is Source System and fall back is LUD and these records created from the UI one by one .

Hi, 

Looking at the screenshot, it looks like the Email.Email survivorship strategy is not able to break the tie to survive just one value. What is the fallback strategy configured ? 

Hi , 

 I have configured the matchfield URI for both Phone and Email in an entity,merged    different records  entities having different Phone and Email. 

They are working expected after merge in both entity and nested-attributes  but after merge Email field is coming with all values where it should have only one where   Phone number is working fine .

They both have same survivorship strategy as below :- 

Email MatchfieldURI:- 

Data :- 

The fall back for Email/EMail is LUD

Please let us know what can be missing here for which multiple fields are present for Email.

hi @Diparnab Dey, 

Actually the email are from two different entities/crosswalks and I have merged the entities and I have mentioed the matchfieldURI above.

Based on that both parent and Nested attribute(Email)got merged but somehow Email field is showing multiple values where only one should come.

Same configuration  I have done for Phone Number as well and after merging the parent entities . Phone also getting merged and Number field is showing only one value.

Not sure why the same thing is not working for Email field.

Ok, so if you are adding the different emails from the Reltio UI, then it means it's being associated with the same Reltio crosswalk. Now, as both the emails are associated with the same crosswalk, LUD survivorship may not be able to break the tie. 

Can you check two things 

• Use options = showAppliedSurvivorshipRules in get entity API and verify what survivorship strategy is being applied for the Email. 
  
• Also, verify from the Get API response whether the singleAttributeUpdateDate for those two emails are available or not. If available, check if it's same or different. 

The primary strategy  is Source System and fall back is LUD and these records created from the UI one by one .

Hi, 

Looking at the screenshot, it looks like the Email.Email survivorship strategy is not able to break the tie to survive just one value. What is the fallback strategy configured ? 

Hi , 

 I have configured the matchfield URI for both Phone and Email in an entity,merged    different records  entities having different Phone and Email. 

They are working expected after merge in both entity and nested-attributes  but after merge Email field is coming with all values where it should have only one where   Phone number is working fine .

They both have same survivorship strategy as below :- 

Email MatchfieldURI:- 

Data :- 

The fall back for Email/EMail is LUD

Please let us know what can be missing here for which multiple fields are present for Email.