Field not available in form? | Community
Skip to main content
Brett_Carpenter
New Participant
May 3, 2018
Solved

Field not available in form?

  • May 3, 2018
  • 1 reply
  • 5398 views

Hi Nation!

I've got a weird issue happening with a form I'm trying to create. When our instance was initially set up, a boolean field called 'Is Partner' was created. It clearly shows in the Field Management section of Admin and a program is actively using it.

However, when trying to create a form to use that field, it doesn't show up in the list. (see images) What could be causing this?

Here's the field list for the form:

Here's the field in Admin:

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 Brett_Carpenter

Hi @Grégoire Michel !

Got an answer from Marketo Support.

The field “Is Partner” is a standard system managed field. This means you can use them in Flow Steps and Smart Lists, it's not possible to add them to a form because they cannot be directly edited. Only fields that can be edited by users or leads are allowed on a form.

So there you have it. Their workaround is to create a custom field that does the same thing...which seems a little redundant. Would there be a way to create a field that doesn't show up on a lead but can be used as a trigger to add someone to a list?

Example: Have a box on the form that says "Are you a partner" - If they select Yes, that calls an action to add the user to the Partner smartlist, which then updates the 'Is Partner' field.

1 reply

Grégoire_Miche2
New Participant
May 3, 2018

Hi Brett,

The same on all instances ( I ran a couple of tests). It's a default field that exists on all instances. I do not know that rationale that forbids to add it to forms since it's modifiable in a smart campaign flow step and it's not a account field but a person field.

Ask support and tell us what is their answer, if you feel spending the time to enter a ticket.

-Greg

Brett_Carpenter
New Participant
May 3, 2018

Whoops, thought it was only a field on my instance

Sending a ticket in now. Will definitely let you know!