Token diagnosis - why would a custom SFDC field not show up as an available token? | Community
Skip to main content
A
Anonymous
February 15, 2017
Solved

Token diagnosis - why would a custom SFDC field not show up as an available token?

  • February 15, 2017
  • 1 reply
  • 4975 views

We have a custom field on our lead records that for some reason is not showing up in the list of possible token values. Are there any specific requirements for a custom field to be available for us as Marketo token?

I did notice that a similar custom fields is available as a token, with the only difference I see being that this field is listed as being mapped by Marketo (under the folder "Field Management" in Field Mapping:

This field that isn't working is listed as an "Unmapped Custom Field" which I'm assuming is simply because it only exists on the SFDC lead record and not the SFDC contact record. Is that right?

Does an SFDC custom field have to be mapped to both the lead and contact to be available as a token?

Thanks!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Grégoire_Miche2

Hi Greg, I mentioned that it's just not showing up in the list of possible values for the autocomplete. I should also mention though, that we've seen an "invalid token" error when we try to force it and type the token in manually:

     (this error is from a smart campaign flow step)

The field in question is called "RF No. Employees". Is it possible the period character in the name could be causing problems?


Hi Jon,

Num employees field type is number. So it will only accept a number as a token. Are you sure that RF. No Employees field type is a number?

-Greg

1 reply

Grégoire_Miche2
Grégoire_Miche2
Level 10
February 15, 2017

Hi Jon,

Forget about the "field mapping", it is not updated after initial sync and therefore is not providing accurate information.

go to field management / field management and, in the list of fields on the right, search for your new field. It should show up there a few minutes after being created in SFDC (checkin admin -> salesforce that you had a recent sync that completed after the field was created in SFDC).

If the field does not show there, it is very likely that your SFDC admin did not grant the right on this field to the profile of the Marketo sync user in SFDC.

-Greg

A
Anonymous
February 15, 2017

Ah good to know about that not updating...

The field in question does in fact show up there under SFDC Custom Fields, so I'm not sure why it's not working. Are only certain field types allowed? This one is just a string anyway.

Grégoire_Miche2
Grégoire_Miche2
Level 10
February 16, 2017

Hi Jon,

What do you mean by "not working?". All SFDC fields types can be used as tokens. Please provide screenshots of what is not working.

-Greg

Terms & ConditionsAccessibility statement

Loading footer...