Suppose you already have a live pipeline and have decided to sync an additional field and all its historical data from an external system. In that case, you'll need to consider some things to ensure you don't accidentally cause data integrity issues.
When you have a live pipeline and add a new field mapping with both source and destination sides, you could accidentally send out NULL values from Syncari to the external system of record before the actual data makes it into Syncari. This can happen if you have workflows running updates on records in Syncari or even if you have multiple sources in the published pipeline.
To avoid these problems, use the best practices outlined below.
Create a New Field in Syncari
There are multiple ways to create a field in Syncari. But for this article, the GIF below summarizes how to map fields using Schema Studio. See Creating a New Field using Schema Studio for details.
Map Source Side
Even though you might want this field to sync bidirectionally, begin by mapping the source side ONLY. Publish that change and move to the next step.
Now that the new field is mapped to the source side, only run a resync to pull the data into Syncari.
Note: Depending on how many records you have in that object in the external system, the resync can take some time to finish. Plan ahead and run the resync over a weekend if at all possible.
Map Destination Side
Now that we have the source side mapped and all the data pulled into Syncari, let's finish by mapping the destination side. Don't forget to publish the changes made, and voila!
You have successfully added an additional data point to your existing live pipeline.