Ideas

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...

Possibility of evaluating and YTD MTD data without appropriate hierarchy. This is relevant for evaluations of daily data.

For models, some dimension names come as part of the model and the dimension name shouldn't be changed. Therefore the request is for a platform functionality for dimensions to also have aliases, so that the dimension can be referred to by its alia...

The fields for editing SQL code are ridiculously small, especially in the vertical direction. Most people doing development work use a large monitor, so the size of this area should be generous by default. Alternatively, it should be responsive or...

It would be nice to have a checkbox for each row in a job that would deactivate or activate it. Use Case: I have a job with 30 load rows ; let's say that I want to temporarily deactivate the 16th because I suspect it to be wrong. Now I have to del...

Allow spanning of frameset to enhance its possibiliies, e.g. 1 column and 2 rows besides:

It would be helpful, especially for buttons, to be able to design the tooltip variably. This would often save several identical buttons with the same function but with different tooltips. For example, for blind buttons, the reason why the function...

Currently, when renaming a dimension, a List where this dimension is used isn't automatically updated, and then has to be manually recreated. It would be nice if this could be done automatically whenever a dimension name is changed.

The abilitly to upload documents in Jedox is very powerful. However we are lacking the ability to easily display the documents currently uploaded into a particular folder. User want to be able "at a glance" see what has been uploaded. So the abili...

At the moment, Jedox differentiates between uppercase and lowercase in the integrator and treats the elements like two different ones. Example: RepUnit <> REPUNIT -> Table normalization, lookups etc. won't work properly as Jedox raises th...