SOLVED

Salesforce - Marketo sync failed due to field not being visible in SF sync user

Go to solution
Highlighted

Salesforce - Marketo sync failed due to field not being visible in SF sync user

Hi all

 

Issue is as the subject line. The sync between our Marketo and Salesforce sandboxes, which was previously working fine, has stopped. The error appearing seems straightforward enough:

 

The following fields are hidden from the Salesforce sync account markto@xxxxx

 

Object

Event_History

Field

SystemModstamp

 

Edit the visibility permissions in Salesforce for the required fields.

 

However, the feedback from our Salesforce admin is as follows:

 

There isn’t actually an object called Event History, its an additional field history tracking you can enable. Mod stamp is a standard field. Its very strange that the field is suddenly not available to the sync, as it’s not a field that is touched.

We also have three event objects all called event, 2 custom and 1 standard object.

 

Can anyone advise what fields/objects we need to make visible in order for this to work? I've had a look at similar posts on the forum and there seems to be a consensus that the Marketo error is misleading and this field could actually be something else. Unfortunately we don't know what!

 

Any help or advice much appreciated.

 

Thanks

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Marketo Employee

Re: Salesforce - Marketo sync failed due to field not being visible in SF sync user

Marketo doesn't support History objects; unfortunately it doesn't stop you from trying. Disable your Event History objects from syncing in the SFDC Custom Object menu in Admin and the errors will go away.

View solution in original post

2 REPLIES 2
Highlighted
Champion Moderator

Re: Salesforce - Marketo sync failed due to field not being visible in SF sync user

I would open a support ticket

Highlighted
Marketo Employee

Re: Salesforce - Marketo sync failed due to field not being visible in SF sync user

Marketo doesn't support History objects; unfortunately it doesn't stop you from trying. Disable your Event History objects from syncing in the SFDC Custom Object menu in Admin and the errors will go away.

View solution in original post