1. Home
  2. Data & reports
  3. Integrations
  4. Salesforce (Version 2)
  5. Salesforce Connector Version 2 – Contact Syncing

Salesforce Connector Version 2 – Contact Syncing

Engaging Networks keeps track of which supporters require syncing via an internal ‘last modified’ timestamp.

Engaging Networks then compares Contacts that have been altered, after this timestamp, against EN Last Modified Date on the Contact.

Contact Push

Each hour, Engaging Networks will push supporters who have been altered since the last push.

Only supporters with a Last Name will be pushed, in respecting Salesforce’s minimum Contact requirements.

Duplicate Management

In the initial release, Salesforce native Duplicate Matching handling is not supported directly from Engaging Networks.

Administrators may see the following errors :

FIELD_CUSTOM_VALIDATION_EXCEPTION:Failed to create Account for Contact Raya Tester. Duplicate Alert:-
FIELD_CUSTOM_VALIDATION_EXCEPTION:Failed to create Account for Contact Jim Tester. Use one of these records?:--
FIELD_CUSTOM_VALIDATION_EXCEPTION:A record with this email address already exists.:Email --

For initial integrations, be sure that ‘active’ Contact segments are brought over to Engaging Networks, prior to launch. This will reduce the need for Engaging Networks creating new Contacts.

Legitimate cases of duplicate matches will need manual administration currently. There are plans to add ‘Enhanced Duplicate Matching’ within Engaging Networks. Intended release of this feature is 2020 Q4.

It is important to note that Engaging Networks unique identity is the Email Address. Allowing multiple Contacts with the same email address will lead to update issues.

Contact Pull

Engaging Networks will pull Contacts whose EN Last Modified Date has been modified since the last ‘pull’ has occurred.

There are two workflows that require setup to help with this process.

Contact Id Lookup

A unique addition to the Salesforce sync is on import, Engaging Networks first utilizes the Contact’s Id to check for existing supporters. If a match is found, the supporter will be updated.

A good use case for this use is a Contact Email update.

Supporter A and Contact A are linked and have the email address test@gmial.com

Updating Contact A’s email address to test@gmail.com, will update Supporter A’s email address in Engaging Networks.

Engaging Networks see Email Address as the unique identifier.

If Contact B does not yet exist in Engaging Networks (or Contact Id does not match an existing supporter) then their Email Address will be used as the next identifier.

Merging Supporters and Contacts

Currently automatic merging is not supported between Engaging Networks and Salesforce.

If merges are required, it is recommended to first merge the supporters in Engaging Networks and then merge the respective Contacts in Salesforce. It is important to make note that the correct Contact Id remains on the Engaging Networks’ supporter’s record.

Common Errors

“INVALID_CROSS_REFERENCE_KEY:invalid cross reference id:–“

The supporter in Engaging Networks has an invalid Id stored in Contact Id. Clear out the Contact Id via Lookup Supporters or replace with valid Id from Salesforce.

“FIELD_CUSTOM_VALIDATION_EXCEPTION:Failed to create Account for Contact Jim Tester. Use one of these records?:–“

On trying to create a supporter in Salesforce, via the API, duplicate matching has been prevented due to a similar supporter being present.

For initial integrations, be sure that ‘active’ Contact segments are brought over to Engaging Networks, prior to launch. This will reduce the need for Engaging Networks creating new Contacts.

Legitimate cases of duplicate matches will need manual administration currently. There are plans to add ‘Enhanced Duplicate Matching’ within Engaging Networks. Intended release of this feature is 2020 Q4.

Updated on September 8, 2020

Was this article helpful?

Need Support?
Can’t find the answer you’re looking for? Don’t worry we’re here to help!
Contact Support