Persistence of filtering, sorting and pagination values

[germede]

After saving a table record, the page is automatically refreshed: all filtering, sorting and pagination configurations are lost. In order to find the last created / edited record the user has to filter, sort and paginate manually again.

It may be a solution to store those filtering, sorting, and pagination values on the URL as GET parameters, so:

• the page can be refreshed after saving a record without limiting user experience.
• one could theoretically store that URL as a "table view" or save it as a bookmark.

[GoOz]

Strongly agree on that. I did some editing on only 30 entries and it was frustrating.

[OSINT-Musings]

I bumped into this issue myself and strongly concur. Tangentially related is #35 which was pushed to the roadmap.

[MageAtoru]

Persistance of filtering is a much nedded function, on top of this one maybe a setting to change default sort ordering from "oldest to newest" to "newest to oldest" entries...

[datenangebot]

Yes, this will come with the view feature. Stay tuned, 2023 will be great.