Linking a Custom Object to Salesforce Record Id | Community
Skip to main content
Ben_Neal1
Level 2
April 11, 2018
Question

Linking a Custom Object to Salesforce Record Id

  • April 11, 2018
  • 1 reply
  • 4668 views

I'm creating a Custom Object in Marketo and want the custom objects to be associated to the Marketo Person/Lead. I would like to link this custom object to the Person/Lead using the "SFDC Id" field which is a GUID from Salesforce. The SFDC Id field is available and accurately populated with the Salesforce record Ids on the Person/Lead, however, this field is not available as a link field in the Custom Object when I'm attempting to map it. There is an "Id" field available for linking, but I think  that's referring to the Marketo GUID - this field is not listed in field management so I'm unsure.

Am I missing something here, or is this a limitation I'm experiencing with Custom Object linking.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

pavel_plachky
Level 5
April 11, 2018

I do not think you can use SFDC Ids to link custom objects in Marketo. Could you create the custom objects in Salesforce and then synchronize the custom object from Salesforce to Marketo?

Ben_Neal1
Ben_Neal1Author
Level 2
April 11, 2018

I should have stated that the source of the custom objects is Salesforce. The native Salesforce-Marketo custom object sync doesn't support what I need so I'll building a custom integration populating a Marketo Custom Object with the Salesforce data. I can easily get the Salesforce record Id field into the Custom Object, but don't know why they wouldn't let me link to the Person/Lead based on the Salesforce record Id.

Grégoire_Miche2
Level 10
April 12, 2018

Hi Ben

The native Salesforce-Marketo custom object sync doesn't support what I need

What is it you cannot do here ?

You can use a secondary ID field that you create in SFDC, formula, value = casesafeid(id) and use it a foreign key for your custom object. But I do think that fixing the original issue and using the custom sync is a much better way to go (starting with maintenance issues on the long term).

-Greg