It would be great to have the ability to use more than one list in a view. An example use case is that I would like to organise accounts on rows the way I would like to see them as an end user with some calculation columns for ad-hoc KPIs but stil...
Lists are a great way to make better use of views accross the system. However, in planning situations it is most often necessaary to compute whether or not a cell is open for data entry. The style/format of the modeler is not sufficient there. For...
Enable attributes or aliases in dynatables / views
Currently there are only the element codes available for dynatables aka views. Would be nice to also have the option to show attributes or aliases instead.
If I want to move a dimension, I only want to see the option where I can move it to and not the current group. Right now I can choose the current group as well, except for when the item is at the last position, but then it is still showing the cur...
It would be nice to be able to define an element in an hierarchy as standard element. This would mean that when splashing on the parent the full value would be written on this element rather than splashed onto all the underlying elements. This wou...
VIEWS: It would be going far beyond better analysis, if you could write back/splash input in a VIEW, even if POV Multiselect is being used with one or more dimensions. The selected elements of one dimension would temporarily be treated as siblings...
Use default subset for a dimension in Paste view dialog
We would like the ability to select a default subset for a dimension when pasting a view. The current "Default subset" option for the dimensions (found in the dimension's properties) can only be used in a ComboBox, Dynarange etc.
Add the ability to create a new subset (Private or Public) in the Select Elements UI. This is where most people would want to create a quick picklist without having to go into modeler. This would really be handy(and is how TM1 does it now)
Prevent saving view as "global" / public if it contains private subsets
Users can select a "private" subset to use in a View for one of the view's dimensions. Since the subset is private, it's only usable for that specific user. If they would now save this View as "global" (meaning, all other users can see & open ...
It is not always required for an end user to see all the list elements in the columns. I will be helpful to have the ability to filter on list elements so that users can choose what they would like to see.
