Filters Do Not Persist

[jho-md]

Describe the bug
When selecting an option for a filter, the filter works as expected. However, when you navigate back to the filter, the filter appears unset rather than showing the previously selected option.

Steps To Reproduce
Steps to reproduce the behavior:

1. Configure a collection with a dropdown filter.
2. Create some sample entities.
3. Choose one of the dropdown choices for the filter and see that the filter works as expected.
4. Navigate back to the filter and see that the filter appears unset rather than persisting the previous selection.

Expected behavior
Navigating back to the filter should persist the previous selection.

Environment (please complete the following information):

• Server OS: Windows
• Browser: Chrome
• Umbraco Version: 15.3.0
• Product Version: 15.1.2

---

This item has been added to our backlog AB#51958

[nathanwoulfe]

@jho-md and again with the pending PR. Will aim to wrap up a few more issues and get a patch out soon.

[acoumb]

Hi @jho-md ,

This has been fixed with version 15.1.3 of UI Builder.

Thanks,
Adrian

[jho-md]

@acoumb @nathanwoulfe Just upgraded to the latest and still having this issue. After setting the filter and applying, I click on the filter again and it appears unset.

[andrejd22]

@acoumb same, issue still exists. This issue is partially resolved. Now, after clicking on a collection item, opening the modal, and then closing it, the filters remain as expected. However, if the user navigates to a different collection and then returns, the filters are lost. This might be acceptable behavior, but in previous versions (13.x.x), filters were saved in Local Storage. We had a custom field implementation with a button that, when clicked, would apply the filters and open the collection with the filtered items. However, this is no longer possible in the current version. Since Local Storage based persistence no longer works, maybe query string parameters could be used to apply and persist filters across navigation?