Brian_Law_MKTO_0-1654988869281.png

Creating a Microsoft Dynamics Data/Field Dictionary

Brian_Law_MKTO
Marketo Employee
Marketo Employee

A team member asked me if there was an easy way to create a data/field dictionary for a Marketo/Microsoft Dynamics native integration and unfortunately there isn't. In this article I will explain how to understand the field mapping between Microsoft Dynamics (MSD) and Marketo. 

 

When you export all the fields using “Export Field Names” you will get an excel field with the REST API, SOAP API and Friendly Label. 

Brian_Law_MKTO_0-1654988869281.png

Fields with no SOAP API name are Marketo only. Many seem to be Marketo Microsoft system fields, Marketo system fields and a few which I’m unable to explain. Here's an example of some of them.

Brian_Law_MKTO_1-1654988931048.png

Fields which include an (a) in the Friendly Label should be account fields.

Brian_Law_MKTO_2-1654988959789.png

You can verify field mappings manually be looking them up in Field Management

Brian_Law_MKTO_3-1654989016654.jpeg

Fields with a (c) in the Friendly Label should be a contact field and may be mapped to a lead field.

Brian_Law_MKTO_4-1654989192314.png

The default fields (aka standard fields) which are already in Marketo before the integration should be mapped to either Lead, Contact or Account. Many will be mapped to multiple entities.

 

This article will explain standard field mappings. 

 

Unfortunately you have to manually look up all the other fields in Field Management since they could be a Marketo only custom field or Microsoft custom field.

363
2
2 Comments
MillenaSiq
Level 2

Thanks for sharing! 

Michael_Florin
Level 10

Couldn't you add the synced field name to the export?

 

And you're saying that "Fields with no SOAP API name are Marketo only." While that might be true, there are also Marketo only fields that have a SOAP API name, right?