Re: Saleforce mapping to Person object rather tan Lead object

Anonymous
Not applicable

Saleforce mapping to Person object rather tan Lead object

Hi Marketo gang,

I have noticed that the object type mapping is now displaying as 'person' rather than 'lead'. As below

Screen Shot 2017-02-09 at 14.45.52.png

Could someone please explain what the difference is, if any?   It doesn't appear to have made a dent on any of the fields which weren't discontinued at the end of last month, but the new inferred country has not synced as expected.

Any advice?

4 REPLIES 4
Grégoire_Miche2
Level 10

Re: Saleforce mapping to Person object rather tan Lead object

Hi Mitchell,

The field mapping screen does not update over time and therefore provides obsolete information. See

You should go to admin -> field management and review the mapping of you key fields. If you have performed the recommended operations before Jan 31st, you fields should be mapped with SFDC fields that are prefixed with "mkto71" and not "mkto2".

If this is the case and you fields seem to not sync anyway, then it can be related to the Marketo user accessing the fields in SFDC.

Now, with regards to the person object, it makes NO difference at all. Marketo Lead used to map with lead and contacts in SFDC. The Marketo lead has simply be renamed as Person, but the mapping is unchanged.

-Greg

Anonymous
Not applicable

Re: Saleforce mapping to Person object rather tan Lead object

Hi Greg,

We created and mapped to mkto71 and everything looked right for the switch over on the 31st.

All of the mkto71 fields in SFDC have for for some reason overwritten as mkto2.

Any further ideas?

Grégoire_Miche2
Level 10

Re: Saleforce mapping to Person object rather tan Lead object

You might be looking at the wrong place.

Please provide screenshots of the mapping you see in admin->field management->select the field.

It should look like:

pastedImage_0.png

-Greg

Anonymous
Not applicable

Re: Saleforce mapping to Person object rather tan Lead object

Hi Greg,

No luck. It seems that something went wrong in our cross over. We did update all the records to begin with mkto71 but it has updated to mkto2 and therefore not updated.

Screen Shot 2017-02-09 at 16.54.38.png

I have raised a ticket with support.

Thanks for your help.

Mitchell