You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to improve the user experience of sorting columns in data tables (e.g., in views like "All Biens Immobiliers"). Sorting should be a fast, seamless operation. Currently, the behavior disrupts the workflow, especially on tables with many columns where horizontal scrolling is required.
Current behavior
When a user clicks on a column header to apply a sort, the entire page reloads or the table completely refreshes its state.
This causes two major issues:
Loss of horizontal position: The table scroll resets, meaning the user loses sight of the column they just sorted if it was located far to the right. They have to scroll back manually.
Unpredictable sort direction: Clicking "Sort" doesn't specify the direction (Ascending vs. Descending). If the user gets the wrong direction, they have to click again, wait for the reload, lose their scroll position again, and scroll back again. This wastes a significant amount of time.
Expected behavior
No page/table reload: Applying a sort should update the data asynchronously (optimistic UI update or simple data fetch) without resetting the scroll container's horizontal position. The user's viewport must remain exactly where it is.
Explicit sort directions: Instead of a single "Sort" button that toggles unpredictably, the column header menu should offer two explicit options: "Sort Ascending (A-Z / 1-9)" and "Sort Descending (Z-A / 9-1)". (Alternatively, clicking the column header directly could toggle between Asc, Desc, and Unsorted, with a clear UI indicator (arrow) showing the current state).
Technical inputs
UI/Scroll State: Modify the table component (or the Apollo Client/GraphQL cache update logic) to ensure that refetching data upon a sort mutation does not unmount or reset the scrollLeft property of the table container.
Menu Options: Update the column dropdown menu component to replace the generic toggle sort with two distinct MenuItem components: Sort Ascending and Sort Descending.
Mutation/State Update: Ensure that clicking these options directly sets the specific orderBy direction in the view's query parameters (e.g., AscNullsLast / DescNullsLast), rather than relying on a toggle logic.
This discussion was converted from issue #21621 on June 17, 2026 13:32.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Scope & Context
We need to improve the user experience of sorting columns in data tables (e.g., in views like "All Biens Immobiliers"). Sorting should be a fast, seamless operation. Currently, the behavior disrupts the workflow, especially on tables with many columns where horizontal scrolling is required.
Current behavior
When a user clicks on a column header to apply a sort, the entire page reloads or the table completely refreshes its state.
This causes two major issues:
Expected behavior
(Alternatively, clicking the column header directly could toggle between Asc, Desc, and Unsorted, with a clear UI indicator (arrow) showing the current state).
Technical inputs
scrollLeftproperty of the table container.MenuItemcomponents:Sort AscendingandSort Descending.orderBydirection in the view's query parameters (e.g.,AscNullsLast/DescNullsLast), rather than relying on a toggle logic.All reactions