I have currently enabled state saving on the filters of a dashboard. While users appreciate it they also would like to save their personalized view which they create by adding or removing columns from the dashboard.
This is how a user currently uses the dashboard->
A user adds/deletes/rearranges the columns as per their requirement:
However, I currently have state saving enabled for only the filters - which is why only the filter for country is holding. I tried enabling state saving for the Filtered Objects but for some reason the column configurations are returning to default view i.e. all columns are being displayed.
In your Object Table widget’s configuration panel, you can scroll all the way to the bottom and toggle on Variable-backed column visibility. This will require a new String Array variable.
Finally, you’ll be able to find the API names of the columns you want from the Column Configuration section of the widget’s configuration panel. The moment you toggle on Variable-backed column visibility, a button near the top-right corner of the first column entry that reads “Show API names” will appear (in the screenshot below it says “Hide API names”). The API names will then appear in a light gray font color within each column entry.
Hi, I use this feature since few weeks and I’m happy it has been implemented because my user also asked for it.
Now I have some user feed backs I would share:
User can’t know if the table state will be saved or not (app designer have to inform them or they have to try to add column then save state, then reload, then understand if column setting was saved or not). In the same way they don’t know which other variables will be saved (e.g. filter)
User can be lost when some table have state saving mode activated and other have not (they can become mad if they do a long configuration and lost it because state saving is not activated). Especially in application with several tables where some tables are configured and other are not. Also when they use 2 different applications where one save the columns selection and the other don’t.
State saving also save at the same time other variables that designer have defined to be saved (e.g. filters) but user don’t exactly know what the state saving will save and it can turn them crazy when for instance they have saved a filter then few days after they they define table columns while a bad filter is selected and clic on Save button. They can lost the filter and the memory of what filter was the good one. (Especially on shared states)
Finally, my users also complain that state do not save the column width and the table sorting.
This feature is great, I hope it could be improved.
