Microsoft Dynamics Custom Field Integration

[Anonymous]

We are working on a MS Dynamics Integration with Marketo. Marketo has been around for a few years independent of our previous (dinosaur) CRM so now that we have a "decent" CRM, we're trying to integrate.

We got a Sandbox of Marketo and IT hooked it up to our CRM Dev environment. They "pressed go" and now I'm checking the integration. 

For custom fields, should I have created those in Marketo FIRST? Some existed in CRM already and are now in the "Microsoft Custom Field" entity of Marketo. Whereas others I've created after are now in the "Lead Info" entity. This is a real mess when looking at an individual lead record, because I want some of these to be grouped together. For example, I have a "Certification" checkbox field and I want "Certification Date" below that. But now the fields are in two different tabs of the record.

Am I stuck with this the way it is? Should I have created any custom fields in Marketo first? And, if/when I do that, will they always be in "Lead Info" (I can't move them to another entity?). I want to make sure I get this right before they "press go" on the Production side and it's really messed up.

[Josh_Hill13]

Heather,

I can only speak for SFDC systems, but I suspect there are similar issues. In SFDC, there are several kinds of fields that you see from the Marketo perspective:

1. SFDC/Standard Marketo fields that link up automatically
2. SFDC Custom Fields - your special fields that Marketo doesn't have a standard map for.
3. Marketo Custom Fields - fields you create in Marketo, but are NOT in SFDC and do not sync to SFDC

To get #1 or #2 to work right, you have to create those fields in SFDC first.

When you say "Lead Info" I assume you are referring to the Marketo Lead Detail View. If you want to group fields together, you can go to Admin > MS > Custom Layout and place fields the way you want. Then, on the Lead Detail View in Marketo, you should see a list of fields in the order you prefer. It is not possible to otherwise customize the views there.

[Anonymous]

Hi Josh,

Thanks for your reply! When I say Lead Info, I mean the way fields are grouped into entitites within field management - i.e. the "folders" - I have Company Info, HIdden Fields, Lead Info, Microsoft Custom Fields, Microsoft Lead Field and Opportunity Info.

In our previous instance, we only had Lead, Company and Opportunity, but our old integration didn't work well so we saw ever fields under Lead or Company. So, I expect to see more and understand I can customize the views. I just want the fields to "live" in the right folder, if that makes sense? Or, since I can create custom views, does it not matter where they actually "live"? Seems tricky from a mapping perspective to have multiple entities (folders) for custom fields (i.e. some are in Lead Info, and some are in Microsoft Lead Field).