New UX Dependent lookup not cleared when main field is changed to NULL
book
Article ID: 241800
calendar_today
Updated On:
Products
Clarity PPM SaaSClarity 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:
Navigate to New UI
Configure Project Type and Project Category columns on Project Grid view
Select a value for Project Type (eg. Major Project)
Select appropriate dependent value for Project Category (eg. New Development)
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,DE79457 ,DE55737
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:
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')
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.
Note: The other impact of having this enabled is Charge Code on the Task object is being set as NULL after an update on the task and its tracked via DE79457 and DE79457 is targeted to be fixed in 16.2.2 scheduled to be released in May 2024 and backported to 16.1.3 patch 2 targeted to be released in April 2024