Field pipelines are the next level down in your unified customer data model and enable you to interact with the fields in each entity pipeline. This is where you define the mapping between the fields within the entities from the various synapses you have connected to Syncari. Field pipelines run in response to changes in the field.
You can create simple pipelines with the Field Mapper or access more advanced features by working on the field pipeline in the canvas. If you created pipelines automatically, Syncari set up field pipelines for each entity.
Configure the Source Side of Field Pipelines
Follow these steps to set up a field pipeline with a source-side node. See About Field Pipelines for details about the features you can use in field pipelines.
➡️ To create a field pipeline with a source-side node:
- Select the Syncari node in an entity pipeline.
The right panel shows a list of fields in the Syncari entity. - Click the field you want to access from the Field Pipelines list in the panel on the right.
- If prompted, click Create Pipeline draft.
- Click Sync from Entities.
- Drag a source synapse to the left of the Syncari node on the canvas.
- Select the node you just dragged to the canvas, and then click Configure Node in the panel on the right.
- Select the field from the synapse that matches the field in the Syncari entity, and then click Save.
- If you want to include a destination, go to Configure the Destination Side of Field Pipelines. Otherwise, the field pipeline is complete. Explore more advanced field pipeline features in topics like Field Functions.
Configure the Destination Side of Field Pipelines
➡️ To configure the destination node in a field pipeline:
- Click Sync to Entities.
- Drag a destination synapse to the right of the Syncari node on the canvas and connect it.
- Select the field from the synapse that matches the field in the Syncari entity, and then click Save.
- Select the node you just dragged to the canvas, and then click Configure Node in the panel on the right.
- Select the field to map in the pipeline.
- Click Save Draft.
Repeat the configuration steps to add a field to the destination side. When complete, your field pipeline might look like this:
Sources and Destinations
Field pipelines inherit the source and destination configuration of your entity pipeline. This means that if you define your entity pipeline with a source node only, then your field pipelines will only have those source nodes available for configuration. If you define your entity pipeline with source and destination nodes, then your field pipelines will have both source and Destination nodes available for configuration.
Example Source Node Configuration
Let's say your business objective is to sync the value in the Account Name field from Salesforce to Syncari.
To achieve this use case, this data pipeline must specify the Salesforce Account Name field as a data source for the Syncari Account Name field.
Therefore, when an Account record is created or updated in the Salesforce Account object, the sync cycle will recognize the changes on that record and create or update the Account Name value in the Syncari Account Name field.
Example Destination Node Configuration
Let's say your business objective is to sync the value in the Syncari Account Name field to Salesforce.
To achieve this use case, this data pipeline must specify the Syncari Account Name field as a data source for the Salesforce Account Name field.
Therefore, when an Account record is created or updated in the Syncari Account entity, the sync cycle will recognize the changes on that record and create or update the Account Name value in the Salesforce Account Name field.