Curious to hear what the communuty says. We noticed the same thing in our instance (same set-up with SFDC leads and contacts) with Country and Country (L). I essentially hid the Country field from Marketo and only use Country (L). So far this works, but not sure why it is the case.
This is a common problem when the Lead-Contact mapping in SFDC is not done properly. These are called Orphaned fields.
You can have L, C, and A. These fields only appear on the corresponding object, so if you had two Job Function (L) and Job Function (C), you will have to use ANY to pull people.
What you want to do is go into SFDC and map the Job Function field on conversion. You may have to create a Job Function 2 on both objects, map them, and then ensure they are mapped in Marketo as "Job Function 2" with both objects on the field in Marketo.
Support can help you fix the original fields, but they will have to remove that field from all assets.
Thanks, Josh. I logged a case to see if Support can help us with this. We do have access tied to the Contact version of the field, but not the Lead versions. I am hopeful they can copy data from the (L) version to the other and then update the other to map to both Contacts and Leads. We'll see!
I contacted support and they fixed me right up.
Hey Josh, I was in a similar situation with two Marketo fields - one normal and one with a (C.) I changed the SFDC API name to match the API of the first one. It's now mapping one Marketo field to both Lead and Contact fields in Salesforce.
Is this going to mess up any data updates from Marketo to SFDC?
And is this why I can only see the overlapping picklist values in Marketo?