If you have an application which has a default sort order specified and you run/launch a mini app with an app setting which filters on a few fields and specifies the sort order profile to be used when the app is run, would you expect when filters are applied in the mini application and the user manually removes the default sort in the UI and adjusts a few filters, that the sort should be excluded in the fetch to the DB? Or, is it expected to always apply the default sort from the application even if the sort was cleared in the UI?
However the user has requested data is how the query will ultimately work. The default sort is for assisting users in the way they commonly look at data, but it can be overridden with another sort or cleared.
Whatever the application and app setting have defaulted as filters and sorts will apply on the first query in the list view, but any following query will be a result of the user specifying different filter and sort criteria.
This is also why the Index Query Restriction setting is applied to many large tables, as it prevents users from sorting or filtering on a column that could lead to poor performance. That can be circumvented, of course, when using advanced filters in the top-left menu.
@ross Thank you for confirming! I am seeing something different happening, so wanted to check before submitting a ticket. Will submit a ticket shortly, thanks!
Circling back to this, and when the user clears a sort, the expected behavior is actually that we fall back to the sort that was set by the Application/App Setting. We felt like this was the better user experience, rather than falling back to sorting by nwId (the empty sort) since those are typically not displayed and don’t have a readable meaning.
Happy to discuss changing this behavior, but I believe what you’re seeing is expected.
I am seeing something different happening, so wanted to check before submitting a ticket. Will submit a ticket shortly, thanks!