Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
List fields do not support choices - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • List fields do not support choices
KB0656550

List fields do not support choices


1157 Views Last updated : Jul 22, 2025 public Copy Permalink
KB Summary by Now Assist

Issue

A configuration that is becoming more and more common is using a List type field (like watch_list) with choices. This is being done to create a sort of "multiple choice" field but it is not a supported configuration and can lead to problems.

Some of the problems that this can cause are:

  • Choices in the list may show their value instead of their label.
  • Scripted logic performing operations against the mis-configured field do not function as expected.
  • Choices are not translated properly.
  • Unable to set the field value via template.

Cause

These issues come up because the List field type was not designed to be used in this way. It is a reference field and the only supported configuration is that it is set up as a reference field.

Resolution

Make sure the field is configured properly in the the system dictionary.

1. List fields are reference fields so make sure you have a valid reference configured.

2. Make sure there are no choices defined in the Choices related list.

3. Make sure that the choice list specification is set to "none".

If you're used to using these fields as "multiple choice" fields, the best way to accomplish this without going against the design of the data type is to create a choice table and define the choices you need there. Then, configure the field so that it references that table and remove your old choice configurations.


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.