If you add new sources to the batch data product or perform additional curation work on the batch results, you will likely want to update the System of Record with those changes.

Tamr provides two options for updating the SOR from the batch data product on the System of Record Management page:

1. Recommended: After ensuring your data product results are ready to be committed to the SOR, run the Stage Changes workflow, review change details, and then run the Apply Changes workflow.
2. Not recommended: Enable automatic updates, which commit changes to the SOR at the end of each data product run.

Why are automatic updates not recommended?
With automatic updates enabled, you do not have an opportunity to review the changes that will be applied to the SOR.

Additionally, updates are staged and applied as the last step in the data product refresh. If either staging or applying the changes fails, the entire data product refresh fails and needs to be re-run.

Tips for Applying Changes

In the UI, Tamr prevents you from running the Apply Changes workflow in these circumstances:

• The data product has been run since the Stage Changes workflow ran. In this case, the staged changes are out of date. Run the Stage Changes workflow again to stage the latest updates.
• No changes were identified by the Stage Changes workflow. If the total number of changes is 0, you cannot run the Apply Changes workflow.
• You attempt to reapply the same set of staged changes. Tamr does not allow you to re-apply the same changes, even if you cancelled the Apply Changes workflow or it failed. Re-run the Stage Changes workflow to regenerate the update.

In any of these circumstances, if you attempt to run the Apply Changes workflow via the API, the job will run but will not submit any operations against the records in the SOR.