Engaging Networks Mapping + Push to EN legend

From EN Salesforce Integration
Revision as of 19:40, 7 September 2017 by Danatengaging (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

1. Name of the mapping

2. Sync direction

3. Format Name

When a CSV file is received by Engaging Networks through the import API, the Format Name is how Engaging Networks knows how to map 'column X', in the CSV file, to 'field Z' in Engaging Networks. On installation, the push mapping has some default options listed in the dropdown. However, Engaging Networks does not yet no anything about 'SFDC_IMPORT' or 'SFDC_CONTACT_IMPORT etc'. You must upload a file into Engaging Networks and 'save' the format as one of these options to create the link.

4. Create CSV

Generate the CSV file, based on the Push query filters and the relevant mappings. To review and download this file, head to Mapping Templates and then the respective mapping. Look for the area called 'Notes and Attachments'.


5. Push to EN

Generate the CSV file and attempt to push the file to Engaging Networks. This step will only work if the CSV file being pushed, matches the Format Name that is saved in Engaging Networks

6. Push query filter

Specify the query rules of the relevant sObject. It's recommended to use a logical ruleset, which pushes 'what is required'. This could be a date or a workflow checkbox, that indicates to the mapping that a contact requires updating in Engaging Networks.


7. Decode values

This option allows values to be replaced. In the example below, if MailingCity is blank - then [CLEAR] would be instead used, which would clear whatever value is stored.


8. Which fields on the sObject should be rendered to the CSV file, that will be imported in Engaging Networks.

You will notice that some fields match logically to what is trying to be pushed. Firstname to First Name is a good example. On other occasions were there is a custom field, you can use the 'supporter data n' options as the placeholders.  Think of the values in this dropdown as just the headers of the CSV file. Once you import this file into Engaging Networks, and save it with an appropriate Format Name, Engaging Networks will then know how to map 'supporter data 1' to the correct field.


9. Field to Update

Once the push job occurs, update a field to indicate the sObject has been 'processed'. This field can either be of boolean or date type. 

For example, create a checkbox field on the Contact object called 'Synced to EN'. A workflow then sets this field to 'FALSE' if certain fields are updated on the Contact object. Under the Push query mappings, then have the filter 'Synced to EN' = FALSE. This would find all Contacts that require processing and attempt to push to Engaging Networks. As the connector pushes the batch, the respective Contact 'Synced to EN' checkbox is then set to TRUE.


Engaging Networks Mapping + Push example