When a user opens an account in the Spoke Org, the Spoke Org uses the REST service to check for updates to fields that are specified as part of enrichment settings in the Master Org. The list of fields that are updated in the Master Org after the previous synchronization appear on the page. The Spoke Org stores the previous synchronization timestamp in the

MultiOrg Last Update From Hub

field. The user can choose to apply or ignore the updates received from the Master Org.

To synchronize all records in a Spoke Org with the Master Org, you need to run a batch job from the Spoke Org. When you run the batch job, it uses the REST service to check for updates to fields that are specified as part of enrichment settings in the Master Org. The batch job gets updated field values for all records in the Spoke Org and performs field-level updates for each record. The batch job does not consider the value in the

MultiOrg Last Update From Hub

field. Instead, the batch job uses the batch number to track updates from the Master Org. After a batch job is complete, all records processed by the batch job must have the same batch number, which indicates all records in the Spoke Org are in sync with Master Org. The batch number is not updated for records that failed. The subsequent batch job picks up the failed records and if the records are processed successfully, the batch number is updated accordingly. The failed records are tracked by using Last Processed ID in the custom settings of the Spoke Org.