Changes to Marketo Salesforce Sync – Questions and Discussion

[Anonymous]

Actually, there are like 20 records with a score, but it's 8. I had hundreds of leads scored with scores from -10 to 80. This is a disaster.

[Mike_Reynolds2]

Christine Jacobson​ Sorry to hear that you had problems with this. I'd definitely open up a case with Support so we can check it out directly and see what happened. Can't really troubleshoot here, but Support's available and can get right on it.

Contact Marketo Support

[Mike_Reynolds2]

Hi all, Group 2 starts later this week. Just checking in to see if anyone had any other questions we can answer. If your Account String starts with A, B or C, you'll be kicking off in September, which is right around the corner! Let us know if we can help in any way

[Anonymous]

Group 2 here. So I've read through all the documentation and am comfortable with the upcoming changes. However the only thing I can't seem to find anywhere is what the actual API names need to be on the new fields we create. I plan to recreate probably 14 or the 16 fields, so I just need to know what the naming convention should be for them, thanks!

[Mike_Reynolds2]

Hi Scott Shapiro

The API names are all listed in the documentation Adding Marketo Fields to Salesforce Enterprise/Unlimited Edition

The first 3 are listed in Step 6

And then the rest are all listed down below in step 13

Let me know if you have any other questions at all!

Mike

[Anonymous]

Hello Mike,

This field naming thing is turning out to be very confusing, we have a support case also open, and they are advising opposite to what you are saying. In the document “https://nation.marketo.com/docs/DOC-3836” says to use the original API names that these fields already had. But SFDC will not allow us to create new fields with same API name as original unless we delete original 16 fields. Our original fields’ API names have the prefix mkto2_, but here you are saying above to use the field API names with mkto71_ prefix. Can we create new fields with mkto71_ API name prefix, and Marketo will pick them up, even if the original fields installed by MLM package had mkto2_ API name prefix.. We do not want to delete the original MLM package fields before creating the new one, because if we delete them first, our layout, formula fields, and reports using them have to be modified and may even be deleted, while if we delete them after the new fields are created, we can simply replace the old field reference with new field reference, and our users will see no impact.

We opened a ticket to support and they said that we will need to delete the fields first before new fields can be created with the exact same api name as original. While you are suggesting that we should create new fields before deleting the old ones. Please confirm if we can create the new fields with mkto71_ prefix in api name, (while the original fields had mkto2_ prefix for api name), and it will work? Or do we have to create new fields with the exact same API name as original as referenced by the document https://nation.marketo.com/docs/DOC-3836.

Thanks in advance for your expert clarification.

[Mike_Reynolds2]

Hi Anurag Khemka​

I'd like to clarify, when you're recreating the new fields, you'll need to use the specific API names called for in the doc, Adding Marketo Fields to Salesforce Enterprise/Unlimited Edition.

You aren't recreating the fields using the existing API names.

In the "Under the Hood" documentation, the relevant line says "You’ll need to create new custom fields in SFDC for the Marketo data to sync into, using specific API names to match up to the original Marketo fields." I'm sorry if there was confusion with that part, but what it means is that the API names you'd create in SFDC need to be exact matches for what is used by the Marketo fields. That lets the new SFDC fields remap over to the original Marketo fields, but it doesn't mean you'd be using the same API names on the SFDC side.

Those new API names are all listed in the doc here: Adding Marketo Fields to Salesforce Enterprise/Unlimited Edition

Hope that helps!

-Mike

[Anonymous]

OK, Mike, Thank you.

I think I am still not 100% sure. Let me make sure again, we need to create the fields with mkto71_ prefix in API name (like mkto71_Lead_Score) as specified in document "Adding Marketo Fields to Salesforce Enterprise/Unlimited Edition " and the screen shots above. Please note that the confusion also came from your comment in the discussion on this document on August 24 "As far as creating API names, adding "mkto71_" to the start of the API name is not required. It's what was used in the examples here specifically to connect them to these other fields in Marketo to match the names in this document."

You stated here "but what it means is that the API names you'd create in SFDC need to be exact matches for what is used by the Marketo fields", if I see under admin section of my Marketo instance, I see that score field is mapped to crm as:

CRM Field Map:

mkto2__Lead_Score__c (SFDC Lead)

mkto2__Lead_Score__c (SFDC Contact)

And API name mkto2__Lead_Score__c is linked to fields already created in CRM by the MLM package. So the Marketo field is using mkto2__Lead_Score__c as the CRM API name, but I cannot use that for the new field as it is already used in CRM.

So you seem to be saying that if we create new fields with mkto71_Lead_Score__c API name, Marketo will recognize it and Marketo fields will releave the mkto2_Lead_Score__c api name, and latch on to the mkto71_Lead_Score__c API name?

I hope I am able to explain where my confusion is?

Please confirm that the new fields should be created with exact API names with mkto71_ prefix as  in "mkto71_Lead_Score__c". and the Marketo 'Score' field will recognize this as a new field and attach to it, even though its CRM mapping currently says "mkto2__Lead_Score__c" which is the API name of the MLM package field.

I just want to doubly make sure before we make change.

Thank you.

[Mike_Reynolds2]

I think I see where part of the confusion is coming from. That specific response was in reply to a different person's question regarding a different custom field, not associated to this configuration change. They had created a field called "package" in Marketo and were trying to get it to connect to a field on the SFDC side that hadn't been created yet. Their use case wasn't related to the MLM Package change here, so it can be ignored.

So the short version is, you'll want to follow the steps exactly as laid out in Adding Marketo Fields to Salesforce Enterprise/Unlimited Edition  with the API names exactly the same as what's listed in that doc.

I know that the existing / current Marketo fields use the field names starting with "mkto2__" but part of the configuration change being made is enabling a special function to change that API name for these specific fields once the new ones with the "mkto71__" names are recreated. It's a function only being applied here for this configuration change. Once you recreate the new fields using the exact API names specified in the doc, the sync picks up the new fields based on the API name and hooks them to the existing / current Marketo fields.

If it's helpful, please feel free to Contact Marketo Support if you want a Support Engineer to take a closer look.

[Dawn_Richcreek]

I did not see that we had to wait until our window to create the new fields so i created 3 of them already. I have questions/concerns:

1. Will the sync use our salesforce API calls? I am worried we will max out on API calls due to the sync. It needs to sync real slow if this is the case.

2. I already have the "Lead Score" field in salesforce of course. When I go to map the lead field to the contact field it gives me 2 fields with the exact names name to map to "Lead Score". It is the same problem with Acquisition fields. Is there a trick to determine the correct one to choose?