Ideas

if you want to edit the next or the previous function in ETL client, you have to close the current one, and click on edit for the following. This would be helpful to jump to the next or previous one without closing the window

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.

Double spaces are not permitted in a dimension element due to the Jedox restriction. Currently this leads to troubles but noone sees it directly. It would be great, if Jedox generates an error message for dimension elements which act against the r...

With the "Jedox Instance Synchronization" feature, users can copy information from one instance to another, including the scheduler. https://knowledgebase.jedox.com/jedox/maintenance/synchronization.htm After copying from the test environment to t...

When you bring up a Drill Anywhere View, make it an option to then Drill Anywhere again. This will be very powerful and allow one to drill to driver cube level.

It is important to be able to extend the ability to synch models beyond just the current region (you cannot right now). Clients may want to have back up instances in different regions. I wanted to transferer a model from US to Germany Instance and...

In the Picklist we have the option to add extra elements. I would like to propose the option to also being able to deselect from a feature similar to this. This will make removing technical members from dropdowns, like "~" and many others, simpler.

A virtual dimension always has a certain structure. - <attribute name>-- Total <attribute name>--- <attribute value>---- <base element>-- No <attribute name>--- <base element> While this is good enough for data ...