New UX Dependent lookup not cleared when main field is changed to NULL
search cancel

New UX Dependent lookup not cleared when main field is changed to NULL

book

Article ID: 241800

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

Dependent lookup field value is not cleared when the value of main field is changed to '--None--' in New UI.

Steps to Reproduce:

  1. Navigate to New UI
  2. Configure Project Type and Project Category columns on Project Grid view
  3. Select a value for Project Type (eg. Major Project)
  4. Select appropriate dependent value for Project Category (eg. New Development)
  5. Change the value of Project Type to '--None--'

Expected Results: The value of field 'Project Category' should be cleared out as it is dependent on field 'Project Type'. 

Actual Results: The value of 'Project Category' field is not cleared out. 

Environment

Release : 15.9.3, 16.0+

Component : Clarity MUX UI Usability 

Cause

DE65083, DE64184 

Resolution

Fixed in Release 15.9.3 through another reported issue DE55737.

The ability to clear the field is enabled through a database toggle. 

    • By default this change is behind a toggle.
    • By default the clearing of dependent lookups won't happen.
    • For SaaS Customers, if you want this enabled, please contact Support.  
    • For On Premise Customers, you can enable the toggle using the following steps:
      1. Run the following SQL Update statement 
        update cmn_option_values set value = '1' where option_id = (select id from cmn_options where option_code = 'RESET_DEP_LOOKUP_VALUES')
      2. Refresh the application caches
    • If the dependent lookup field is configured as a 'Required' field, clearing the value is not possible and the value will remain in the database. 

Additional Information

For More details related to DE55737: Dependent Lookup not cleared in New UX  

Attachments