Most functions in Syncari operate on the current entity or the current field that is being processed. The functions covered in this article can get data and update data in other places. These include...
Lookup Reference Data - lets you access static lists of data you have uploaded to your account.
Lookup Syncari Record - lets you get data from any record that has been synced to Syncari.
Update Syncari Record - lets you Lookup and then change values on one or more records in Syncari.
The Lookup Reference Data Function
Reference Datasets in Syncari are CSV files you can bring into the platform. They're mainly for storing data that doesn't change often or is outside your connected systems, like translations or airport codes.
Similar to the Lookup Syncari Record function, the Lookup Reference Data function lets you pick a field to match synced records with a reference record and then retrieve a specific field value from another column in the reference dataset.
Creating a Reference Dataset
- Create a CSV with each row acting as a record and each column as a field
- Navigate to Data Studio and click on the + icon next to the Reference Data dropdown
- Give the dataset a name and click the Upload CSV button to upload your local CSV
Lookup Reference Data in Field Pipelines
By employing the Lookup Reference Data function, you can easily cross reference and replace field values of synced records with those from reference records.
Components of the Lookup Reference Data Function
Field Reference:
- Display Label: An optional field where you can provide a descriptive name of the lookup being performed
- Description: An optional field where you can explain the purpose of the lookup in more detail
- Dataset: A required field where you'll specify the dataset against which you want to look for a match against the current record being synced
- Lookup Key: A required field where you'll specify the column in the reference dataset where Syncari will look for a match against the synced record's field value
- Destination Field: A required field where you'll specify the column from the dataset whose value you want to return if a match is found in the Lookup Key column
- Default Value: An optional field where you can specify a default value for a field if no match is found within the reference dataset
- Ignore Case: An optional flag that will recognize a match between a synced record field value and a lookup key value regardless of capitalization
- Operator: An optional picklist where you can specify matching conditions by 'Exact', 'Contains', and 'In'
Lookup Syncari Record
The Lookup Syncari Record function should be used when you need to access a value from another record that has been synced to Syncari. Lookup Syncari Record is available on both Entity and Field pipelines. Let's say when a new lead is created you want to see if there is an account it might match. You want to do this match on the domain. The first step would be to create a field on the Lead to hold this value and then the rest would be done in Syncari.
On an incoming Lead record:
- Get the Root Domain from the Lead's email
- Use that to lookup an account with that domain (See this node in detail below)
- Check if we found an account
- If we didn't then just write the lead into Syncari
- If we did then set value on the field we created in Salesforce
Let's look at that Lookup Node from Step 2 in detail:
- Give the node a label (We recommend the word Lookup and then the Syncari Entity you are searching)
- We want to find an Account...
- ...with a Domain...
- ...that Equals...
- ...the value coming from the previous node (Extract Domain from Lead Email)
- Click Save
That's it. After that, you can use a Filter to check if we found an account and the Set Value to assign the found Account ID into the Account Match field.
Components of the Lookup Syncari Record Function
Field Reference:
- Display Label: An optional field where you can provide a descriptive name of the lookup being performed
- Description: An optional field where you can explain the purpose of the lookup in more detail
- Syncari Entity: A required field where you'll specify the entity (outside the current entity pipeline) against which you want to look for a match against the current record being synced
- Filter Conditions: A required field where you'll specify which field on the synced record should have a matching value with the specified field in the lookup entity
- Do not match on blank values: An optional flag that will ignore a match between the synced record and the reference entity, if the synced record has a blank value in the lookup field
- Sort Records: An optional filter that allows you to specify fields on which to order records returned from the lookup, as well as sort direction
- Count Records: An optional flag that will include a count of records returned
Lookup Syncari Records in Entity Pipelines
The Lookup Syncari Record function, when used in entity pipelines, is an effective way to create more complex lookup functions with multiple lookup conditions based on multiple fields. When used in an entity pipeline this function can also be used to prevent records from being created in Syncari at all, unless a match in another entity is found.
In the example below, you can see how this type of filtering is possible within an entity pipeline.
Lookup Syncari Records in Field Pipelines
The Lookup Syncari Record function, when used in field pipelines, can be used to modify individual field values on synced records. The output from the lookup function can be stored in temporary variables, written directly into Syncari record fields, or to destination synapse fields.
In the example below you can see how field values can be easily replaced and stored within field pipelines.
Update Syncari Record
Note: As of 9/18/2023, the Update Syncari Record Function has been changed and is now the Update Syncari Records Action located on the Actions tab when building pipelines. Existing functions implemented in your pipelines will continue to work as designed. You will need to use the new Update Syncari Record action going forward. See this article for more information.
The Update Syncari Record function should be used when you need to change one or more values on another record that has been synced to Syncari. Let's say when an Opportunity stage change we want to update the Account with the highest level Opp Stage, the first step would be to create a field on the Account to hold this value, and then the rest would be done in Syncari.
This pipeline is very basic because the focus for this section is the Update Syncari Record Function. Depending on your needs there may be some logic you want to apply before updating the record.
Let's look at the configuration of the Update Syncari Record node that I have labeled "Update Account Most Recent Stage"
- Give the node a label
- We want to update an account...
- That has a Salesforce ID...
- ...that Equals...
- ...the Account ID from the incoming Opportunity
- When we find the account we want to Update the Most Recent Opp Stage field
- With the output from the previous node which is the Stage from this Opportunity\
- [Operation]
- Click Save
That's it. Now when any opportunity passes through the system this field on the Account will get updated. You can also do this for groups of records. For example, if something changed on a parent, like Account, you can update all the related Contacts.