Prevent a Newly-Synced Field in SFDC From Creating Two Fields in Marketo | Community
Skip to main content
A
Anonymous
July 19, 2017

Prevent a Newly-Synced Field in SFDC From Creating Two Fields in Marketo

  • July 19, 2017
  • 7 replies
  • 2332 views

Issue Description
You want to prevent a situation where you create or sync a new field on the Lead and Contact objects in SFDC and two fields are created in Marketo, one mapped to Lead and the other mapped to Contact.

Issue Resolution
You will see this behavior if the an SFDC field is created on two objects across more than one sync cycle, one before a sync cycle starts and the other one during or after the sync cycle completes. To ensure both the lead and contact show up mapped to the same custom field Marketo, do the following

  1. Disable the global sync in Marketo. (Admin > Salesforce)
  2. Create the field on your desired objects in SFDC.  Make sure they both have the same API name.
  3. Re-enable the global sync in Marketo, allowing the field in both objects to sync down to Marketo at the same time.

If you find yourself with multiple fields in Marketo after the sync, contact Marketo Support to have the fields merged or remapped as necessary.

Who This Solution Applies To

Customers integrated with Salesforce

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    7 replies

    Tylee_Suarez
    Tylee_Suarez
    Level 2
    July 24, 2017

    Thanks for posting this! I'm actually struggling with a similar issue, perhaps you can help? I created a new field at the Account (company) level in SFDC. After sync, the field is showing up in Marketo, but at the lead level. Is there a way I am able to map this field correctly?

    Roxann_McGlump1
    Roxann_McGlump1
    Level 5
    July 24, 2017

    It would be best to open a support case to get help with this, since the documentation team doesn't have access to your Marketo instance.

      Ibti_Bourie
      Ibti_Bourie
      December 17, 2019

      Hi @Roxann McGlumphy,

      In this scenario, do you know if it is a prerequisite to have the lead field and the contact field mapped for conversion in SFDC? 

      Also, I wonder if having different field label in SFDC for the lead and the contact object could result in 2 fields created in Marketo?

      I experienced the following a couple of days ago:

      • the lead and contact fields had the same SFDC API name
      • the lead and contact fields were not mapped for conversion in SFDC
      • the lead and contact fields had different SFDC fields label
      • the lead and contact fields were pushed to Marketo within the same sync cycle 

      It resulted in 2 fields created in Marketo, one mapped with the lead object and one mapped with the contact object. 

      Thank you, 

      Roxann_McGlump1
      Roxann_McGlump1
      Level 5
      December 18, 2019

      Please contact Marketo Support for further assistance with this issue.

      Oz_Platero
      Oz_Platero
      Level 6
      December 18, 2019

      Hello @Ibti Bourie‌,

      In this scenario, do you know if it is a prerequisite to have the lead field and the contact field mapped for conversion in SFDC?  Yes

      Also, I wonder if having different field label in SFDC for the lead and the contact object could result in 2 fields created in Marketo? No. Marketo uses what you have in Mappings for Conversion.  Be sure to turn off bi-directional sync before starting. If you have already completed and it needs fixing Marketo support can remap fields.

      Ibti_Bourie
      Ibti_Bourie
      December 18, 2019

      Thank you for your answers - I did contact the Marketo support when it happened to get them to remap the field and delete the extra one. 

       It might worth it to add in this article to have the fields mapped for conversion in SFDC.  

      @Oz Platero‌ I had however another scenario where the fields were not mapped for conversion, with same SFDC field labels and API name, and it did create 1 Marketo field mapped with both lead and contact.

      Oz_Platero
      Oz_Platero
      Level 6
      December 20, 2019

      Mapped for Conversion is more for SFDC behavior (but does impact Marketo mapping).  In SFDC when you convert a lead it renders that row in the object Read-only and creates a new row in a different Object such a Contact.

      https://help.salesforce.com/articleView?id=faq_leads_what_happens_when.htm&type=5

      I had however another scenario where the fields were not mapped for conversion, with same SFDC field labels and API name, and it did create 1 Marketo field mapped with both lead and contact.

      ** Correct. Default Marketo behavior is to try and pair up fields with the same API name. Mentioned here in this article
      Edit Initial Field Mappings - Marketo Docs - Product Documentation 

      https://docs.marketo.com/display/public/DOCS/Edit+Initial+Field+Mappings#EditInitialFieldMappings-BreakExistingMapping 

      Terms & ConditionsAccessibility statement

      Loading footer...