Neil_Robertson6

Also note that the version of the API which Marketo uses is only v20 - Salesforce is now on v37!!!

As others have noted, it is certainly possible (but no advised) to connect 1 Marketo instance to multiple SFDC instances but it does become tricky if you are not sending information to an ESB or API endpoint via Webhooks etc so you know where to route decisions etc.

We also see this with Custom Object where there is a lot of R/W going on. If the numbers will never match then great please tell us 😉 if the over count is down to delta processing then tell us - but perhaps split the logic up as Marketo Rows being higher than Salesforce Rows doesn't make sense?!

From a Salesforce perspective yes - there is no issue re: compatibility but the fact Marketo is using an older version is detrimental to the fact Salesforce is increasing their feature sets etc. A quick API check of v20 and v36 show a few fields (on account in this case) which are now visible in th...

Not really sure I understand the reply TBH my point is that Marketo accessing (using) a version of the API 16 versions behind the latest Salesforce API (version 36) therefore Marketo is not supporting a lof of new fields (and features) which are present in the latest. There are fields which are p...

REST is always the preferred choice now. SOAP is a legacy deployment. I would also recommend 100% that you always use JSON as payload and response and XML is not well supported in Marketo - especially when it comes to element attributes.

What Marketo can sync and see is entirely dependent on sharing rules and the OWD of SFDC. Note as well though that depending on your SFDC database size that a sync can take anywhere between 1 hour to 2 weeks (seriously) to synchronize fully.

Thanks Sandford - Great JS but only downside I can see is the size limit of a small 64k!

Change #END to be #end (note the syntax highlighting which is showing you it is not correct)