The issue is that there is no way to manage them well.
Our issues are:
All lists are globally accessible. Can we create private lists like we have private views?
Can we have a hierarchy of lists? To make navigation easier than scrolling through piles of irrelevant lists.
Currently, most users can create lists but not delete them. Ideally they could delete lists they created, but not others'
Lists are created at a database level and seemingly cannot be stored at a view level - they become available everywhere in the database which clogs up the view box. Can we have the option to create a list that exists only in a given saved view?
ADMIN RESPONSE
Aug 23, 2024
Thank you for your great idea. While we cannot commit to a specific target version, we will consider adding it to our future internal backlog. If you can add further information about the context of this feature, please add it here so we can evaluate it more fully.
Agree, Lists are a great way to approach and tackle a lot of situations. I would add the following:
Private lists (for user context) are great. Also helpfull would be to create / use a list within a dynatable (view), that is used exclusively in this dynatable. Meaning it doesn't bother anyone else at another point in the system and others are not likely to change this list on accident, what would screw the report
Ease the access for lists. They are currently very hidden. A much more user friendly way to create, use and maintain them would be highly appreciated. Ideally directly from the designer view / dynatable view with understandable ui/ux and maybe even the possibility to adjust (dimension) formattings
Add spacer columns (to have some space between blocks of columns)
Enable data entry based on a calculation (or calculated column). This means, I would like to elaborate, if a given cell should be open for data entry or not. This is usually based on settings in attributes or cubes (planning workflows). A simple evaluation based on user rights is not sufficient for a planning application
Agree, Lists are a great way to approach and tackle a lot of situations. I would add the following:
Private lists (for user context) are great. Also helpfull would be to create / use a list within a dynatable (view), that is used exclusively in this dynatable. Meaning it doesn't bother anyone else at another point in the system and others are not likely to change this list on accident, what would screw the report
Ease the access for lists. They are currently very hidden. A much more user friendly way to create, use and maintain them would be highly appreciated. Ideally directly from the designer view / dynatable view with understandable ui/ux and maybe even the possibility to adjust (dimension) formattings
Add spacer columns (to have some space between blocks of columns)
Enable data entry based on a calculation (or calculated column). This means, I would like to elaborate, if a given cell should be open for data entry or not. This is usually based on settings in attributes or cubes (planning workflows). A simple evaluation based on user rights is not sufficient for a planning application