Ideas

it should be possible to use the localize-function also for check-box, buttons etc.

in #_GROUP_DIMENSION_ cube this is really complex to know what is the right for a certain group since it can be inherited from upper levels, for instance: Europe N West France R this would be great to be able to see that, say using a "flag" t...

Currently rules are calculated in the moment when the user queries the data. It would be great to have the option to shift the timing to the point when the user changes data. So the result of the calculation would be stored/persisted when the use...

Macros assigned to filter-comboboxes (to set dynarange-variables) are executed BEFORE data is updated. A function similar to __open() that is triggered after palo-data has been changed, e.g. in dynaranges, would allow macro-treatment of the new ...

In the case of bar line chart etc. Sometimes the labels of the first chart and the labels of the second chart overlap. Therefore, I want a function that automatically adjusts the position so that they do not overlap.

Currently, when exporting an xlsx file from Excel to the Report designer using the COM add-in. The name field in the dialog is by default empty, if the user clicks export without entering a name, the process starts loading but then nothing happens...

When you change Cube with similar dimensions, in previous versions the identical dimension kept their filters and configuration. In current "best version ever" :-) this functionality has been dropped from the product and the viewpoint is reset to ...

In Modeler in dimension attribut e.g. "Name" should be shown for multiple languages by default or based on selection & activate search functionality. Use case: Currently as a user I need to select each time I open the dimension the Name German...

Currently: Language selection is currently based on the Jedox system. Use case A: Jedox is available for e.g. Korean language, but the build application has only translations for English or German. In that case currently a workaorund need to check...

All actions should have the possibility to have an optional return code/description to provide information about the execution. This could then be sent to a variable/named range/range to be processed in a subsequent action. This effectively allows...