Dynamic dependent lookup behaves differently in List and Details
Article ID: 257440
Updated On:
Products
Issue/Introduction
When modifying a main lookup value in a List view, the dependent lookup gets blanked out in the Details view.
When doing the change in the Details view, the dependent lookup gets blanked out in both the Details and List views
This can be seen with any custom dependent lookup as well as using the OOTB Project type and Project Category lookups
Resolution
Pre 16.1.1
I take a project with both OOTB Project Type and Project Category fields populated.
On the list view I modify the Project type, The Project Category gets blanked out in Details views.
On the Details view I modify the Project type, The Project Category gets blanked out in List and Details views.
In 16.1.1
On the list view I modify the Project type, The Project Category gets blanked out in Details views.
On the Details view I modify the Project type, The Project Category gets blanked out in List view only.
The dependent lookup is not blanked out on the view you are working on, but it does on the other one.
As per 16.1.1 the behavior is coherent
Additional Information
There is an enhancement open
F22900: Enhance Parameterized Lookups in Modern UX
If you change the main lookup, we autosave the main lookup and clear and autosave the values for any dependent lookups (regardless of whether the dependent lookups are on the screen – grid, details flyout, properties, etc.). If the dependent lookups are required, then we will display an API error message with the dependent attribute names so the user knows to complete them to save the record. All future edits to that record should display this API error until the required dependent lookups have values entered and saved. If the user navigates away from that record without entering values for the dependent lookups, then the edit to the main lookup and clearing of the values for the dependent lookups are reverted to the previous values (as if no edits occurred).
Feedback
