In domain-separated instance list view does not retain filters after modifying related list on form - Known Error

In domain-separated instance list view does not retain filters after modifying related list on form Description Personalized Related List layouts does not work with Domain Separation, when "glide.sys.domain.use_record_domain_for_data" is set to "false".

After opening a record from a related list in a domain-separated instance, if the user modifies the list filter or layout (i.e. adding an entry via "Edit..." UI Action) and updates, gets redirected to the original list view with the previously applied filters no longer present.

Steps to Reproduce

1. In a non-domain separated instance, open a list view of Group [sys_user_group] records. 2. Apply any filter (Name contains Network). 3. Open any of the resulting records. 4. Scroll down to the related lists. 5. Select the Group Members tab. 6. Click the "Edit..." button and add or remove an entry. 7. After saving the change, click the Update button on the record. Note that the filters conditions are still applied in the list view. 8. Activate the Domain Separation plugin. 10. Select "TOP/Oceanic Airlines" from the Domain selection menu in the System Settings. 11. Repeat steps 2 - 7. Note that the filter conditions have been removed and the default list view is displayed.

Workaround After carefully considering the severity of the issue and the cost and risk of attempting a fix (refactor of the entire GlideStack/URI stack component), 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 apologise for any inconvenience.

To receive notifications when more information becomes available, subscribe to this Known Error article by clicking the Subscribe button at the top right of this form.