...
To synchronize additional SalesForce.com fields, add a custom tag to a Customer object in LAC. The custom tag must be in the format SF_full_custom_tag_database_name. For example, if you have a custom field named "Currency" in SalesForce.com, the custom tag would be named "SF_Currency__c."
After initial synchronization, synchronization updates are performed at intervals you specify (as described below). During synchronization updates, data changes 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 objects) will not be deleted in SalesForce.com. Therefore, the next synchronization will cause the object 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 in SalesForce.com; the customer object is not deleted.
To enable synchronization:
...
Note that the initial synchronization may take some time, depending on the amount of data you have in SalesForce.com. The status of the synchronization, including its successful completion and any problems, are logged in the History grid. Synchronization from LAC to SalesForce.com makes additions and updates to the SalesForce.com data, but does not delete SalesForce.com data. However, all edits made in SalesForce.com will be made in LAC, including deletions. If you delete an object in LAC that still exists in SalesForce.com, that object will be created again in LAC upon the next synchronization update.
Performing a full re-synchronization
...