You can automatically synchronize Customer and Contact data between LAC and SalesForce.com. SalesForce.com synchronization is enabled and configured using the Administration page.
Upon SalesForce.com synchronization, every Customer object in LAC is given the custom tag "SF_Id," which stores the customer's SalesForce.com account ID. Contacts are matched based on email address. We recommend first performing synchronization on the SalesForce.com sandbox to test for any unexpected results before enabling synchronization in production.
By default, the following fields are synchronized:
SalesForce.com field | LAC field |
---|---|
Account.Name | name |
Account.Phone | phone_number |
Account.Description | description |
Account.Fax | fax_number |
Account.BillingCity | city |
Account.BillingCountry | country |
Account.BillingState | state |
Account.BillingStreet | street |
Account.BillingPostalCode | zip_code |
Contact.FirstName | name |
Contact.LastName | name |
Contact.Email |
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, only data that has been changed since the last synchronization update are propagated from one system to the other, as follows:
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.
Performing a full re-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 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 of. A 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.