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.
Dependent field not clearing out if choice is changed. - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Dependent field not clearing out if choice is changed.
KB0830116

Dependent field not clearing out if choice is changed.


1293 Views Last updated : Apr 8, 2024 public Copy Permalink
KB Summary by Now Assist

Description

App Version : 10.0.2
App: Agent / NOW
Platform :Both iOS and Android

Steps to Reproduce

1. Go to any Orlando instance and agent mobile app.
2. Ensure that you have an applet (active incidents for example) which has an button like example Edit.
3. In this button ensure that we have two fields configured Category and Sub Category.
4. In category select something like Inquiry / Help.
5. In Sub Category select Antivirus.
6. Now change the category to Software , Notice that the antivirus is still there.
7. Since subcategory is dependent on category it is expected that once i change the category the subcategory field will become empty.
8. The subcategory is not getting empty so users are filling in wrong value and submitting the record.

Expected behavior : Dependent field should become empty on change on the first field

Actual behavior : The dependent field is not becoming empty hence use is submitting the wrong choice and causing confusion.

Workaround

This issue has been fixed in the version 10.1.0 of mobile release.


Related Problem: PRB1406371

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.