You can automatically synchronize Customer and Contact data between License Activation Center and SalesForce.com.
To enable synchronization:
- Open the Salesforce Integration tab from the Administration page and enter your SalesForce.com credentials, using your SalesForce.com API security code for the password.
- Select the update interval in the Configuration grid.
Note that the initial synchronization may take some time. The status of the synchronization, including its successful completion and any problems, are logged in the History grid.
Data will be automatically synchronized at each update interval to reflect changes since the last update. You can force a full resynchronization using the Resynchronize button. This will resynchronize all data at the next regular update interval, and is needed only in rare cases. For example, you may want to do a full resynchronization 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. Resynchronization will not remove data from LAC; however, if customer data has been deleted from SalesForce.com since the last full synchronization, that Customer object in LAC will no longer have any relationship to SalesForce.com data.
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.
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.