Salesforce.com fields that are mapped to Acoustic Campaign through the Salesforce.com integration must remain intact or visible otherwise the sync with Acoustic Campaign will fail. The field mapping interface will display unavailable field mappings in a red section titled Fields not found in Salesforce. This means that a previously mapped field is no longer available through the Salesforce.com API's to the Salesforce.com User being used for the integration. You would also notice on the Status tab that the Profile Data for Leads, Contacts and Accounts sync is in a Failed status. The synchronize with Salesforce.com will remain in a failed status until these mappings are fixed.
It is recommended that you check with your Salesforce.com administrator to determine what changes to the field or Salesforce.com integration user's Profile in Salesforce.com caused the failure. The errors could be potentially due to the following four reasons:
- If you have a Professional Edition Salesforce.com organizations, removing the field from the page layout will cause this error since only fields on page layouts are exposed to the Salesforce.com API's.
- Put the field back onto the page layout and the issue should resolve within a few minutes.
- Log out and back into Acoustic Campaign to allow the field mapping interface to refresh.
- The field was deleted from Salesforce.com (all Salesforce.com editions).
- Delete the field mapping(s) from the 'Working Copy'.
- Reactivate the mapping.
- The custom field's API Name has been renamed (all Salesforce.com editions). Most likely the field was renamed by a Salesforce.com Administrator which included both the Field Label and the Field API Name.
- Salesforce.com user interface warns of affect on integration during the rename process. Your options are to either rename the Salesforce.com API name back to what it was or delete the field mapping and then add it back as a new field mapping if your desire is to keep it mapped. The field name listed in the 'Fields Not Found in Salesforce' section within Acoustic Campaign is the API name which it is expecting. That's what you should rename the Salesforce.com custom field back to.
- DO NOT include the '__c', that is automatically appended to the end of a Salesforce.com custom field's API Name.
- The Salesforce.com integration user's access to the field has been revoked. Check the Set Field-Level Security for the Salesforce.com field and be sure the Profile that the integration user is assigned to is checked.
- Once checked, the issue should resolve within a few minutes.
- Log out and back into Acoustic Campaign to allow the field mapping interface to refresh.
Comments
0 comments
Please sign in to leave a comment.