Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

After initial synchronization, synchronization updates are performed at intervals you specify (as described below). During synchronization updates, data changes only data that has been changed since the last synchronization update are propagated from one system to the other, as follows:

  • All additions and updates to data in one system are propagated to the other.
  • Data deleted in SalesForce.com will also be deleted in LAC.
  • Data deleted in LAC (other than customer contacts, as described below) will not be deleted in SalesForce.com. Therefore, the next synchronization will cause the object For example, if a customer is deleted in LAC that still exists in SalesForce.com to be added again to LAC.Customer objects deleted in LAC will delete only that customer object's contacts , any update to that customer's data in SalesForce.com ; the customer object is not deleted.will cause the customer to be re-created in LAC upon the next synchronization update. 

To enable synchronization:

...

If necessary, you can force a full re-synchronization using the Re-synchronize button, which will re-synchronize all data at the next regular update interval. Full re-synchronization is generally needed only in rare cases. For example, you may want to do a full re-synchronization if there are significant changes to your original data set in SalesForce.com, or if LAC enhancements provide new synchronization features you want to take advantage ofA full re-synchronization will also cause any data that was deleted from LAC but that still exists in SalesForce.com to be propagated to LAC. For example, if a customer was deleted in LAC but not in SalesForce.com, the customer (including its contacts) will be re-created in LAC upon full re-synchronization.