Global subsets are currently stored with IDs referencing elements. THis leads to broken global subsets whenever a dimension is loaded in modus update or transfered to the production environment via the new database script functionality.7 votes
For the usage scenario of transferring data with scripts, the subset definition is not be relying on ID’s anymore as of Jedox 7.1.
For retaining the subset after modifying dimensions themselves, larger internal changes are required.
To make use of the new flexible cube layout functionality PALO.EL subfunctions inside the PALO.DATA are needed. Inserting the PALO.DATA with the "Paste Data Function" dialogue thus requires to manually edit this pasted function for each dimension of the cube. It would be nice to have a checkbox or similar in the "Paste Data Function" dialogue to call for automatically inserted PALO.EL subfunctions (either with the default element as chosen by "guess arguments" or the default read element if specified, not sure which would be better).4 votes
We’ve added this request to our feature backlog.
On a per user and per dimension basis information about the last selected alias should be stored and retrieved, when opening a new view.
That would help users to work faster with their data.10 votes
Currently only supported whole positive values are supported for the data filter, e.g. 'Top 10' values. It should be possible to use negative values to define e.g. -10 for 'Flop 10' values. #1533210 votes
- Don't see your idea?