Record Unification

What is a Unified Record?

A unified record is the centralized representation of a particular entity. This can be a person, a company, a sales opportunity, etc.

Why Unify My Records?

The purpose of unifying a record is so that all systems contain the same values for shared fields. For example:

This Person
this.person@company.com
408-489-2204

This Person might have a phone number in one end system but a completely different phone number in another system. A unified record will solve this problem by updating all end systems when one end system is updated.

What is Required to Unify a Record?

1. Define the field (primary key) or set of fields (composite key) that identify a unique record in the entity.
2. The primary key or composite key must exist in every connected end system.

Syncari can only attach one record from each end system to the unified record.

• If a record from an end system cannot be attached to an existing unified record then Syncari creates a new unified record.
• A new unified record also creates a new record in all other end systems configured as destinations in your pipeline.

How?

Now that you have the basic concepts of record unification down, you can configure your Syncari entity pipelines to unify your data. In pipelines, the central Syncari node is the unified record. 

1. Create a draft pipeline and connect your source objects to the Syncari node.
   
2. Add the Attach Record function along each path and configure it with the primary or composite key you decided on for each entity. In this example, I am unifying my accounts on account name and address.
   
   Note: Make sure to grab the tokens for each of your unifying fields from Schema Studio so you can enter them after the Equals operator.
3. After both sources have synced you will see the records in Data Studio that have been attached. When the Salesforce Account or the HubSpot company is updated this one record will be updated.
   
4. Once you have tested your unification and your initial resyncs from the source side have been completed you are ready to connect your destinations.

Attach Record Behavior

We will look at how Attach Record function works in a couple of scenarios. We will use a simpler Attach Record configuration for this demonstration.

• Consider an existing Syncari record with Account Name as SAMPLE.COM and Salesforce ID as 0014x000008247cAAA and Syncari Id as 655b954327e0b900010cedb6. Now a new record comes in from Salesforce source with same Account Name but a different Salesforce ID. In this case Attach Record function does not attach this incoming record with the existing Syncari record. You would use Merge Studio policies to unify these records by using Account Name and Billing Street in "Find Duplicates" condition. See Merge Studio for details.
• In the second scenario, there are two records in Syncari. One record has ID Mappings from both Salesforce and Hubspot and another record from only Hubspot.
  
  Now a change is synced from Salesforce for Account record with ID 001Dk000013X2FEIA0. Account Name for this record is TEST.COM. As you may notice, this record has the same Salesforce Account ID as the first record and Account Name as the second record. As the Attach Record function configuration matches on the Account Name, the Salesforce ID Mapping is removed from the first record and new mapping is added to the second record.