Changes to Marketo Salesforce Sync – Questions and Discussion

[Mike_Reynolds2]

UPDATED: Editing my previous reply -- just saw what I missed before.

Hi Greg,

Apologies --  Looks like I had a copy/paste mistake there. Give me a minute and I'll get it fixed up. Official documentation on the process with correct details is right here: Adding Marketo Fields to Salesforce

Mike

[Grégoire_Miche2]

Hi Mike,

This I know

But the table has the ID field twice, on line 4 and 16th. So either one field is missing or the count should only be 15 fields.

-Greg

[Mike_Reynolds2]

Greg,

The count is 16 fields. I just copy/pasted incorrectly is all. The documentation shows all 16 fields but it's broken into two separate tables, so I had tried to combine them together into one table to make it easier but must have overlapped one line.

The 16 fields listed as the affected fields are the exact same 16 fields detailed in the documentation.

- Mike

[Grégoire_Miche2]

Thx

[Anonymous]

Hi Mike,

I have done all this, do we need to just uninstall the app to continue or await the time we are scheduled in for the uninstall and sync?

Nick

[Mike_Reynolds2]

Nick Mirams​

You'll definitely want to wait until the scheduled time for your company to do the deployment. This will make sure we spread out the workload of the backfill and resync within the right times so that we don't overload the pipelines between our servers and SFDC. If the timing doesn't work, we can definitely accommodate rescheduling it for you, but we want to keep track so that we don't overload other groups along the way. Please Contact Marketo Support and we'll be happy to set up a new time for you.

Thanks,

Mike

[Grégoire_Miche2]

Hi Mike Reynolds,

What will be the version number of the MSI package once it has been upgraded ?

-Greg

[Mike_Reynolds2]

Hi Greg,

The version number won't change from what it currently shows. It isn't automatically upgrading the MSI package, it's patching the dependency for the existing installation to remove the dependency on the MLM package. So if you manually upgrade the MSI package, you'll get an entirely new version number, but the patch that went out doesn't actually upgrade the package, it just corrects that back end dependency, so the version is actually the same.

I think it may have added a ".1" at the end of the version number, but I'm not positive on that point. Arjun Nair​ should know more about that particular detail.

Thanks,

Mike

[Grégoire_Miche2]

Hi Mike,

It would be nice if we could have a clear way to know in SFDC whether the MSI package has been patched or not. And on a compliance / It procedure stand point, it would also be preferable

-Greg

[Mike_Reynolds2]

Greg,

That's actually something that Marketo is actively tracking. The patch has already rolled out - it's already been deployed and is in place.

We've also already identified all the customers who use MSI version 1.38 (there's only 34), which can't be updated by the patch (you can also identify it yourself if you check the doc here for details) and we're developing the communication plan to reach out to those customers to walk them through the upgrade process directly. 

Now, there are also some one-off issues where the patch that went out may not have successfully updated the MSI package. We get data back that indicates this and will have reporting on those cases as well. As with the others, we'll be reaching out to those customers directly.

Thanks,

Mike