Are Custom Objects the best way to handle custom fields that can have multiple selections? (e.g. Person lives in multiple states) | Community
Skip to main content
John_Truong
Level 2
February 20, 2019
Question

Are Custom Objects the best way to handle custom fields that can have multiple selections? (e.g. Person lives in multiple states)

  • February 20, 2019
  • 1 reply
  • 3267 views

Hello all,

We are new to Marketo and noticed that you the default fields do not give the option of creating 1:M relationships. It is a 1:1 mapping as far as I can tell?

We would like to store a contacts geographical foot print. For example, we would have the US Federal Government as a contact person but that person is responsible for multiple states.

The end purpose is to have that person be sent specific state blogs contents based upon the states he could belong to. e.g. Email john.doe@company.com can have California, New York and Utah.

Is the best way to do this is create a custom object with the State a column name and then the link back to that person's email in the Custom Object?

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

1 reply

SanfordWhiteman
Level 10
February 20, 2019

COs are overkill for this purpose. Use a semicolon-delimited String for this field.

John_Truong
Level 2
February 20, 2019

Thank for the quick response sir!

One other thing, we want to sync this with our Custom CRM app. For example, we also have other valuelists that are not standardized but want to put in Marketo for example, a list of business lines we specifically serve. We use lists like these in our custom CRM. The idea is that contacts between both tools share the same valuelist. E.g.if someone were to add an additional value (e.g. like the one above, another state to an email contact in our custom CRM, we could then do an API (possible?) to sync that to the Marketo or vice versa. The reason I liked the CO was that we can store additional data like unique ID's for that valuelist and not just free form text.

However, can we do this syncing with a semicolon-delimited string value too and again am I doing overkill to use COs ?

Thank you,

John

SanfordWhiteman
Level 10
February 20, 2019

If you're trying to share a picklist of possible values that's outside the realm of COs in any case.

That list could be synced to a {{my.token}} which could in turn be used on Marketo forms. However, it wouldn't automatically "prime" any selects within the Marketo UI.