Field Mapping Contacts Salesforce to Emma - Critical Need

  • 2
  • Idea
  • Updated 4 years ago
  • Not Planned
We are a new Emma client and just getting up and running on this.  We love the email design features of the system but we are hopping for improvements to the Salesforce integration.  We understand there are some great new features coming but our current issue is based on syncing contracts for personalization. Leads map fine (Name, Title, Email, Phone, Company....you name it...) When you work with contacts you can not map the company name.  This is a big issue.  I would really list to customize our client (contract) email communication with recognition of the company.  Please please fix this mapping issue? 

Does anyone have a work around that works?

Fingers crossed that this make a future feature list.

Darrin
Photo of Darrin Stern

Darrin Stern

  • 7 Posts
  • 3 Reply Likes
  • frustered

Posted 4 years ago

  • 2
Photo of Katie Lewis

Katie Lewis, Official Rep

  • 3414 Posts
  • 309 Reply Likes
Official Response
Hi Darrin! As you know, we currently we don't allow for mapping between Emma fields and Salesforce lookup or formula fields. There’s really great background on it on our Salesforce FAQs page in the Resource Center that says:

Many common Salesforce fields, such as "Lead Owner" and "Account Name," are actually "lookup" fields. This means that they're not unique to an individual record; they're actually looking up the information that they display from elsewhere in your Salesforce account. Lookup fields are not available for syncing in Emma for Salesforce, and in most cases that's for the best -- You wouldn't want a change in "Account Name" on a contact record in Emma to actually change the name of the Salesforce Account with which that Contact is associated.

Some accounts may also use "formula" fields in their Lead or Contact profiles. Formula fields are used to combine different pieces of Salesforce data using, well, formulas. They're handy for everything from revenue projection to lead distribution, but because the fields themselves are dependent on their independent components to derive the displayed value, a two-way sync with Emma is not possible and, again, probably not desirable -- we wouldn't want to muddy up your formulas.

Our first priority with the Emma for Salesforce integration is getting the Connected App version live. I'm going ahead and sharing this idea with our Product Team to somehow find a way to safely allow mapping from lookup/formula fields through the integration or offer a feature that automatically flows the data in a Salesforce lookup or formula field to a standard text field, which can be mapped. (So, it isn't a mapping issue that needs a fix, but rather a new feature to introduce at some point.) That second part is currently possible within Salesforce, through some custom development on your end. Rather than that being possible only through client-driven custom Salesforce development, I can understand why you'd like to have that available as a feature that comes as a part of our integration package.

I'm so glad you've shared this! I'll keep you posted with news from our Product Team.
Photo of Clean Energy Collective

Clean Energy Collective

  • 25 Posts
  • 3 Reply Likes
How do you map ANY SF field to Emma Audiences?  I added a new contact field for "Stage", but don't see any way to actually map fields.  We cannot take advantage of any automation unless we can trigger on changes/additions into SF - I have Emma groups setup based on SF reports.  Please show me how to map field (just a text field fwiw).
Photo of Emily Hollingsworth

Emily Hollingsworth, Alum

  • 2203 Posts
  • 158 Reply Likes
Hey there -- The field mappings are setup as a part of the Emma Setup process. Those would have been specified when the initial setup and bootstrapping of the integration was done, but you can roll back through that Emma Setup process at any point to update the field mapping selections originally applied. For some guidance on doing that, please refer to Part 3 of the install guide for your version of Salesforce here, and let me know if you have any trouble!
Photo of Katie Lewis

Katie Lewis, Official Rep

  • 3414 Posts
  • 309 Reply Likes
Hi Darrin! I spoke with our Product Team, and we aren't planning to pursue this project. It's complicated because a text field in Emma doesn't know how to read the value from a formula or lookup field, and Salesforce won't convert the field value to a string before passing it over.

I'll let you know if we come up with any workarounds!
Photo of Darrin Stern

Darrin Stern

  • 7 Posts
  • 3 Reply Likes
Thank you for the update.  I will hope enough people vote for this issues to it can raise on the feature request list.  I am not sure how other people who use SF personalize the company name in the marketing efforts with out this feature.  

Come on Emma community please vote for this need - SMILE ;-)
Photo of Katie Lewis

Katie Lewis, Official Rep

  • 3414 Posts
  • 309 Reply Likes
I spoke with our Salesforce admin to see if there's a workaround. He said it's fairly simple for a singular field but isn't scalable for lots of fields.
  1. First, you take the field you want to convert from a formula to a text value. Then create a field to catch its value -- so if it's a text return formula, create a text field, if it's a number return, a number field, etc.
  2. Then add a workflow field updated to update the new landing field.
  3. From there, you'll create the workflow rule. There are two criteria that must happen: It should be monitoring a field that would show a noteworthy change -- if possible, the field itself -- and it should be set to every time the record is created or edited. This will still not cover all scenarios, so if the formula is part of a cross object formula and one of the values on a different object changed, causing a new value on the formula but not actually activating the workflow on the second object. The only way to correct for this would be to have a report that allowed you to look across both values to find anomalies. 
  4. After that, you'll have two fields with the same value; however, the second one would be a text value allowing data manipulation.  If you wanted that value to also populate information back to the formula, you'd need a third field, which could work as an indicator to the original formula or when to mimic the field you're creating. This would probably require some manual work, an export of IDs and a data loader update to a checkbox field would probably work.
Now, all this info is straight from our admin and totally over my head. :) I'm glad to pass any questions back his way!