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.
Reference field dependency does not work with a Dropdown Choice type - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Reference field dependency does not work with a Dropdown Choice type
KB0657565

Reference field dependency does not work with a Dropdown Choice type


4076 Views Last updated : Apr 8, 2025 public Copy Permalink
KB Summary by Now Assist

Description

Custom reference field set as dependent only applies the expected filter if set to suggestion reference type. When set to dropdown reference, the dependency fails and the dropdown list always shows every value present.

Steps to Reproduce

1 - Open an Incident form to configure its layout
 
2 - Create a new reference field, "Service/Module" to the CMDB Configuration Items table:
[task.business_service]
mandatory with default value
simple ref qual
Dropdown reference to Business Services [cmdb_ci_service]
 
3 - Create a new reference field "Sub Module" to the CMDB Configuration Items table:
[incident.u_sub_module]
mandatory with default value
simple ref qual
Suggestion reference to Business Services [cmdb_ci_service]
Dependent on "Service/Module"
 
4 - When changing the "Service/Module" value, and then typing something into "Sub Module", observe the dependency works and the suggestions are correct for the selected Service/Module.
 
5 - Change the "Sub Module" field to Dropdown reference.
 
6 - Observe the dependency stops working, the dropdown field always shows every value, regardless of the value in "Service/Module".  Applying default filter "parent is not empty" or clearing instance cache doesn't change the behaviour.

Workaround

After carefully considering the severity and frequency of the issue, and the cost and risk of attempting a fix, it has been decided to not address this issue in any current or near future releases. We do not make this decision lightly, and we apologize for any inconvenience. 
 
As a workaround, please use Suggestion Reference dependent fields instead of Dropdown Reference.

Related Problem: PRB758180

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.