Marketo and Dynamics Lookup Fields

[Michael_Florin]

Hello all,

I'm struggling with a Marketo/Dynamics native integration. Dynamics uses lookups for certain fields - like Country - and we see GUIDs instead of friendly values on synced down persons.

Any idea why these fields are not editable from the detail view UI? I can change them through Smart Campaigns though.

And secondly: Although we read these GUID values from CRM, we can't seem to insert a lead correctly into CRM with these values. Is Marketo not supposed to insert with the lookup IDs?

I've read through this forum and saw a couple of threads regarding this issue - https://nation.marketo.com/t5/product-discussions/marketo-to-dynamics-hows-that-working-out/m-p/6772...- but I haven't seen a solution. Is there one?

Thanks!
Michael

[Katja_Keesom · Accepted solution]

Hi @Michael_Florin , this is one of the biggest frustrations with the native MSD integration. We were hoping the multi value picker upgrade announced for tomorrow would fix it, but unfortunately we learned it doesn't. There is an idea on the nation that has been there since 2016 and is still under review. The only thing we can do is keep bumping that up: https://nation.marketo.com/t5/ideas/show-value-of-lookup-fields-not-guid-for-dynamics-crm/idi-p/2628...

I've had terrible trouble with it as well, with new issues popping up every time you think you have it figured out. We are now going to test Dan's idea of a munction formula to transpose the guids into the friendly values, even though officially the munction functionality is also not officially supported: https://nation.marketo.com/t5/product-discussions/dynamics-fields-showing-hashed-values-in-marketo-s...

[Matjaž_Jaušove2]

Yeah, that would be a major improvement.

[Michael_Florin]

Being an open idea since 2016 or being on an "Implementation Plan" since 2017 is so frustrating. It means that nobody cares...

Thanks for responding, guys! I was fearing exactly that. I'll keep on digging and experimenting and talking to Marketo Support. It feels to me as if creating workaround fields with clear names in MSD is the best way to go, but unfortunately my client doesn't have the best grip on their tool, and it's a HUGE organization. A change like that might take them two years...

[Katja_Keesom]

Formula fields could indeed be a useful workaround...