Enable more sync options between Marketo and Microsoft Dynamics CRM | Community
Skip to main content
Dan_Stevens_
Level 10
February 23, 2016
New

Enable more sync options between Marketo and Microsoft Dynamics CRM

  • February 23, 2016
  • 4 replies
  • 5379 views

There are many useful sync options that are available to SFDC CRM environments:

But for MS Dynamics environments, there's just one: "Sync lead to Microsoft".

The lack of these additional options really has our hands tied for including specific activity within our smart campaigns and flow steps - specifically "change owner", "create task" and "Delete lead".  Please enhance the sync capabilities between Marketo and MS Dynamics.

4 replies

Grégoire_Miche2
Level 10
February 23, 2016

Hi Dan,

+10

To be added to these:

-Greg

March 16, 2016

Hi Dan-

I agree. I don't know if you could help me out, I'm new to Marketo Dynamics integration and I'm struggling that Lookups fields show up as the GUID. You would think by now there would have been a fix for they instead of the customer having to do a workaround.

Can you help push up votes on mine request?

Thanks!

-Jennifer

Dan_Stevens_
Level 10
March 16, 2016

Hi Jennifer - we've been trying to get this to work in our instance for months now.  And finally did - but only in our sandbox environment.

In order for you to use the same approach, you will need to ask Marketo to enable "Munctions" for your environment.

See this discussion thread for more detail: Syncing "friendly" custom entity values from MS Dynamics CRM

March 16, 2016

So, you would need to enable munctions, then also pay a monthly fee to a third party? Just want to be sure I'm ready that right.

Thanks for the info. This is a lot less integrated than I thought.

February 6, 2020
No text available
Edward_Camarill
Level 2
February 15, 2020

It's odd how all these old ideas have suddenly re-appeared. 

But since, as I understand it, Munctions are dead to Marketo. Is there any alternative to translating GUID-like values in DCRM Entity Syncs? Or are we stuck with the solution suggest by  Grégoire - additional fields in DCRM to hold the text values of the original fields?