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 want to allow users to customize the order of visible columns. While we might eventually want to allow users to drag columns around, we are thinking about doing this in a popup for now (similar to #2325 where we're adding a button to recordset page to customize sort in a popup). There are two UIs that we could think of:
In the popup, we will display a list of columns. This list could have columns not already visible on the page (a new context, perhaps?). Users can click on a column to toggle its visibility. They can also drag a column and reorder them. Clicking on submit should adjust the displayed table.
Another option is to show two different lists. One is the pool of columns and the other one is the actual visible columns list. And users can just drag columns around.
Regardless of the UI, the computed order should be stored in the local storage. We most probably want to store the order per page. So, for example, in the related section, users might want to see different visible columns than the recordset. Eventually, this state should be stored in the database as part of the overall personalization feature that we would like to have (this needs more thought).
Another way to achieve reordering of columns is to use ag-grid for our recordset tables. But that requires more exploration and would require more refactoring than the feature we discussed. It also won't allow us to handle the toggle visibility of columns (we can just remove them and not add them). So we're going to do this in a popup for now.
The text was updated successfully, but these errors were encountered:
We want to allow users to customize the order of visible columns. While we might eventually want to allow users to drag columns around, we are thinking about doing this in a popup for now (similar to #2325 where we're adding a button to recordset page to customize sort in a popup). There are two UIs that we could think of:
In the popup, we will display a list of columns. This list could have columns not already visible on the page (a new context, perhaps?). Users can click on a column to toggle its visibility. They can also drag a column and reorder them. Clicking on submit should adjust the displayed table.
Another option is to show two different lists. One is the pool of columns and the other one is the actual visible columns list. And users can just drag columns around.
Regardless of the UI, the computed order should be stored in the local storage. We most probably want to store the order per page. So, for example, in the related section, users might want to see different visible columns than the recordset. Eventually, this state should be stored in the database as part of the overall personalization feature that we would like to have (this needs more thought).
Another way to achieve reordering of columns is to use ag-grid for our recordset tables. But that requires more exploration and would require more refactoring than the feature we discussed. It also won't allow us to handle the toggle visibility of columns (we can just remove them and not add them). So we're going to do this in a popup for now.
The text was updated successfully, but these errors were encountered: