This is an awesome launch control check list Grace Brebner‌!! Legit. ... View more

Good day Adam Monago​ - good question! In my experience there is a very specific field to denote the primary contact related to an Opportunity for Marketo to see the relationship. That field is the customerid field in MSD on the Opportunity, a standard field. If you use a custom lookup field Marketo doesn't know that that field's purpose is to connect the Contact and the Opportunity. Please let me know if you have resolved this, or if I can help you further on this! Regards, PW ... View more

Good day Dan Stevens​ I wonder if there might be a "behind the scenes" issue at play here. A couple of weeks ago I learend the following from Marketo support: "When Marketo attempts to pass either an insertion or an update into the CRM through the API, we adhere to the deduplication rules in both cases and this can cause the API request to fail. In Marketo we have the option to suppress deduplication configuration when we make the API request for inserts for Leads, updates on Leads or Contacts, or a combination. We adjusted the configuration in the Marketo instance to suppress deduplication configuration for updates on both the Lead and Contact entities." So if you add a case comment on your open issue and mention that Praveen had pointed the above out on another case then this may help if the de-dupe rules may be affecting how the API calls are happening. Hope this helps some! PW ... View more

Quick question for you Dan Stevens do you have duplicate detection rules active in DCRM? ... View more

Good day Jeremy Foote​ - that's a challenge! I have seen 3 possible scenarios work ranging from high to low tech. The first scenario is to write a web hook that calls a web service that would change the statecode of the related DCRM record. So the payload of the web hook would be the GUID of the record, and the new state code. In Marketo you would use a trigger to call the web hook when you have an update to a "disqualified" record. I rank this as the highest tech solution. The next approach I have seen done is using an ETL tool like Bedrock Data to write a task related to the disqualified record, and then have a workflow in DCRM that then changes the statecode. This approach does rely on having an additional technology (I checked Zapier and it unfortunately doesn't allow for a trigger from Marketo on record update). I think this would be the mid-tech solution. The last approach I have seen used is the manual method where you would define an alert email that would be sent to a human that includes a link to the DCRM record, and the human would then manually re-activate the disqualified record. Let me know your thoughts Jeremy Foote​! PW ... View more

Understood! Thanks - I developed a similar plugin for DCRM years ago, and a few computers ago. I am going to see if I can dig that back up and post it here if I do. PW ... View more

Great approach Grégoire Michel​! Would you be willing to share the recipe for the MSD plugin with the DCRM MUG? Thanks! PW ... View more

Good to know Dave! I would love to know more about why/how this didn't work for you. I am about to onboard a client with existing rules so insights into the impact would be so helpful! PW ... View more

Hello Dave Cunningham​! In Dynamics you do have the ability to setup Field Security Profiles. I haven't yet used this feature but I did find this tool tip from Microsoft on how to set them up. Let me know if you get this working! Paul Wilson ... View more

Good day Greg! Apologies - when I was replying last night I had misread your initial question to mean that you couldn't merge in DCRM. Next time I go to reply I will wait until I get a good night's sleep and re-read first! I had a client a few years ago that had an issue merging records in DCRM because of a custom plugin they had deployed. Their only course of action was to delete the DCRM record, and we then had a smart campaign in Marketo to run clean up for records marked as Microsoft is Deleted. Merging in DCRM is the best approach as noted by you and Dan Stevens​. I don't know of any CRM Fusion Demand Tools like applications for DCRM, perhaps we should build one! Hoping to see you at Summit next month! PW ... View more

Grégoire Michel​ The approach I have had to take a few times now is to identify dupes in Dynamics, then delete those records in Dynamics, and then delete the linked Marketo record. When you go ahead and delete the Microsoft record you then can see that the Microsoft record was deleted in Marketo, and delete it in Marketo. Unfortunately this has the consequence of loosing all the activity history in both Marketo and Dynamics for the record(s) sacrificed. If anyone has a better approach, I am all ears! PW ... View more

Thanks Dan - pretty cool actions (were they available) right? I was sent this by a former colleague who got it as a screen shot from a youtube video their Marketo rep sent them. By the time I was send the link the video was removed from youtube. Funny you mention change owner - I have built a workaround to accomplish that and will be helping my colleague to setup the same thing in their environment. It is in no way ideal (given the delays between Dynamics and Marketo if you want to send an email alert to the new record owner you're 25 minutes all in from the start to the end of the protocol) but it does get the job done. Working on a few other frustrating point including add to list and setting source campaign WITHOUT needing to reference the actual GUID... Hope that Marketo can beef up the MLM so we get some of these functions soon! Cheers! PW ... View more

Having this not supported in Marketo is a huge disadvantage in how Dynamics and Marketo interact. I echo Michael's question - is this on the roadmap? ... View more