Hi Community, we're running into an issue with Salesforce custom object sync, when it got sync'd down to Marketo, it got split into two separate ones, one under Lead and one under Contact object. And we can only enable one or the other since they share the same name. I know there's a poll about this missing feature, but at the meantime, is there any workarounds on this? I saw someone mentioned about changing the Custom object name under Lead or Contact in salesforce, is that even possible or what's the implications?
Or, can I sync the custom object associated with Lead, and sync a second layer object of the same custom object associated with Contact? (I tested this one with a smart list, doesn't seem like it pulls up the Contact records I need)
Any ideas? Thanks a lot!
Solved! Go to Solution.
Hi there,
The trick is really that simple: just click on the name in the UI prior to sync to give the two objects distinct names. As you mentioned, you'll have to think about the custom object as being fully separate every time you reference it (whether that's in a Smart List, with Velocity, via the API, etc.) but otherwise there shouldn't be any hiccups.
Hi there,
The trick is really that simple: just click on the name in the UI prior to sync to give the two objects distinct names. As you mentioned, you'll have to think about the custom object as being fully separate every time you reference it (whether that's in a Smart List, with Velocity, via the API, etc.) but otherwise there shouldn't be any hiccups.
Thank you Courtney! This trick does work. What is this name that I'm changing, Marketo object API name or just the label?
Also, changing the object name in Marketo, is there anything on the Salesforce side we need to be aware of?
Again, thanks so much for sharing!
Hi there,
So, the name being changed is simply the label Marketo gives the object itself (the API name should not change.) It basically needs to be separate for UI purposes as well as to note that the objects do not map together across both Lead and Contact. There should be no impact on the Salesforce side.