I am not sure I am following you here: the fiest name and last name are rather standard fields of the person object, not of acustom object.
When you create a new CO in Marketo, it comes with no field.
I would not encourage you to have a second set of first and last name fields in the CO, unless you really need them (for instance because you to manage multiple persons attached to the primary person object)
Also keep in mind that CO have some limitation In the way they can used, especially with triggers And in velocity scripts.
Fields on Custom Objects aren't duplicate fields, Steve. They're fields that are associated with an individual Custom Object, thus are many-to-one with Leads. If you want to only store one First Name, so all connected COs always use the Lead's First Name, this field should not be on the CO.
Thanks Greg and Sanford.
The confusion I am having is that I am passing in information that is one to many (such as product purchased name), but I also want to pass in email address, so I can match the product purchased name against the email address (which may or may not already be in Marketo).
So my confusion is, how can i pass data for fields that already exist (such as email address) in through the custom object? It sounds like I don't need to (and shouldn't) create a custom object email address field.
I still have a lot to learn about custom objects. Thanks both for your input.
1 of 1 people found this helpful
You can and should link the custom object to the person object using the key you want here. It might be the email address, but pay attention if you have duplicates in your person database.
If you are gathering the last and first names and want to update the last and first names in Marketo, then just do that through the API for the lead (person) object, and not in the custom object.