Marketo and Salesforce mapping changes before initial sync | Community
Skip to main content
Level 2
March 13, 2018
Question

Marketo and Salesforce mapping changes before initial sync

  • March 13, 2018
  • 2 replies
  • 4696 views

Hello,

I am working on the initial setup of a new Marketo and Saleforce sync. I have not done the initial sync yet, because I am stuck on step 4 where you define the field mappings. When I was checking that the Marketo fields that I created in Salesforce were mapping correctly, I realized that one of my field API names had a typo and thus was not mapping correctly. I went back to our Salesforce development environment and fixed the name and made sure that the lead object was mapped to convert correctly to a contact. I asked the Salesforce admin to move this to the production instance (I don't have admin access to the production instance and therefore can't make changes or see API field names). Now when I have checked back in Marketo, there seems to be no change to the fields and the mapping is still wrong, even after I reset the schema. Does this mean that he didn't move the information to the production instance or are there other steps that I need to take in Marketo to fix this before doing my initial sync?

Thank you for any help that you can provide!

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

2 replies

Dan_Stevens_
Level 10
March 13, 2018

Did you disable and re-enable the sync in Marketo as well?

arw90Author
Level 2
March 13, 2018

I never actually enabled it, so I am not sure how to disable it. Here is what I see on the Salesforce screen:

Any recommendations of how to disable the sync?

Thanks!

Grégoire_Miche2
Level 10
March 13, 2018

Hi Adam,

I do not think you even need to. The SFDC connector is self healing, meaning it can automatically handle when a field seems to have been removes (which is how it sees a field which API name has changed).

I would proceed with the sync. The new field (i.e. the renamed one) will also be normally mapped. The worse case scenario would be that both the old and new fields are created, in which case the support can help you and "deep hide" the field you do not need any more (meaning it will disappear from your UI).

-Greg

arw90Author
Level 2
April 12, 2018

It has been about a month, but to circle back on my original question: When there was a change of the Salesforce api name during the initial sync Marketo was able to figure out the changes and remap the fields correctly after the changes had been made in Salesforce. If anyone runs in to this issue, I would suggest making the necessary adjustments in Salesforce as soon as you realize there is a mistake and before starting the initial sync. Fixing the API names during the initial setup made it so that we didn't need to engage Marketo support to remap or "deep hide" fields.

Thanks for your help!

-Adam