SOLVED

Blocked Field Updates: FULL NAME vs. FIRST NAME

Go to solution
Jenn_DiMaria2
Level 10 - Champion

Blocked Field Updates: FULL NAME vs. FIRST NAME

When I search for fields to block updates to, FIRST NAME and LAST NAME don't appear as options. Instead, I've blocked all field updates to FULL NAME unless they're made in SFDC (our master database).

However, the FIRST NAME and LAST NAME fields were overwritten on a Static List import. How can I block updates to these fields with the only NAME option I find in my field list is FULL NAME?

Thanks in advance!

1 ACCEPTED SOLUTION

Accepted Solutions
Frank_Breen2
Level 10

Re: Blocked Field Updates: FULL NAME vs. FIRST NAME

I think the fields are just called First and Last

first-last.jpg

View solution in original post

3 REPLIES 3
Frank_Breen2
Level 10

Re: Blocked Field Updates: FULL NAME vs. FIRST NAME

I think the fields are just called First and Last

first-last.jpg

View solution in original post

Jenn_DiMaria2
Level 10 - Champion

Re: Blocked Field Updates: FULL NAME vs. FIRST NAME

You're right. Wow. Well, that's nutty since they're not referenced as such anywhere else I've seen. Thank you!

Dan_Stevens_
Level 10 - Champion Alumni

Re: Blocked Field Updates: FULL NAME vs. FIRST NAME

That's where it gets confusing - that the API name usually differs from the name of the field in "field management" and why it would be useful for Marketo to provide the API name ( ).  For example, when you want to use FIRSTNAME in a token, {{lead.First Name}} is the correct name.