Merging in Reltio by Using the Salesforce Merge Service
Merging in Reltio is done in two scenarios by using the Salesforce merge service.
- Child syncs to a loser entity attribute that is not merged with an attribute, which is synced to the winner or another loser account’s child. In this case, the child moves to the winner account in Salesforce and an appropriate child crosswalk changes the contributor from the loser entity to the winner entity.
- Child syncs to a loser entity attribute that is merged with an attribute, which is synced to the winner or another loser account’s children. In this case, the child is removed to avoid duplicates.
Example
There are two entities that are synced to Salesforce accounts. The
Email attribute from both the entities is synced to separate
custom objects in Salesforce. Email is a child of an account in Salesforce. One of
the email value is the same between the two entities and is merged after the
entities merge. The following image shows the state of entities and accounts before
merge:
Entity #1 to Account #1
Entity #2 to Account #2
Entity state after merge in Reltio but before merge processed by the Salesforce merge service
The image above shows that the merged entity has two Salesforce crosswalks related to two
different Salesforce accounts. One account will be identified as a loser and will be
deleted from Salesforce. The merged entity has three values for Email after merge.
Email with Type = Person and Email =
person@reltio.com was present in both entities and merged because the
values matched. This email relates to two different custom objects in Salesforce,
one from the winner and one from the loser.
Entity state after merge processed by the Salesforce merge service
The image above shows that the account with ID 001f400001FM1UXAA1
was identified as the loser and was removed from Salesforce. An appropriate Salesforce
crosswalk was marked as deleted.
Winner account state in Salesforce after merge processing
The winner account received only one email from the loser with ID
a04f400000FndeAAAR. An appropriate crosswalk with ID
a04f400000FndeAAAR changed the contributor from the loser to
the winner. The second email from the loser with ID
a04f400000Fnde9AAB with the same fields was removed because it
was already present in the winner. An appropriate crosswalk with ID
a04f400000Fnde9AAB remains in the loser contributor and gets a
delete date. The winner account and all the children are updated with OV values.