Skip to main content

When a user changes the sorting of a grid to a different column, it is usually because the users wants to find the rows with the highest or lowest value of the sorted column. When you have a grid with multiple pages in the Universal GUI, the current behaviour of the GUI leads to confusion/frustration because it automatically changes to the page the selected row is on after applying the sorting. Many times the selected row is somewhere halfway the page and thus the user scrolls up to find to the highest/lowest values of the sorting, but if the user didn't notice the pages changed it are not the actual first rows. 

 

Idea: When changing the sorting, select the first row of that sorting. Or at least make a config setting for this.

 

 

@PeterKeeris Interesting topic you're bringing up here! Have had quite some discussions on this one internally already. I believe we can distinguish two Use cases of the Grid:

  1. Data manipulations on a specific row, where the user should stay on the same row / if not found, same row index / if not found, last row.
  2. Search/filter/sort actions on the dataset where a user is looking for different record(s) than the currently selected row.

​​​​​​As far as I'm concerned, in the second Use Case I expect that after Sort / Filter / Pre-filter change / Quick filter / Combined search the GUI always selects the first row of the first page. 

I'm curious to learn whether the Community agrees with us @PeterKeeris!

New→Open
Terms & ConditionsCookie settings