Ideas

In a waterfall chart, it is difficult to read the added or subtracted values if the starting value is large. These running values are relatively small compared to the starting value. It would be nice to be able to add a break (with slanted lines o...

Hi, I have found that Copy paste functionality in macro editor in jedox web doesn't interact with Clipboard, this means we cannot copy the code into notepad and edit it outside the macro editor. There are buttons for copy and paste but they don't ...

A PALO.DATA function refers to single base or consolidated elements for aggregation. It would be fine to be able to define subsets of elements to get a sum of these,

The rule editor is very powerful but hard to understand from a business user point of view. The user interface could be improved in terms of usability and structure. A grouping of rules in a folder structure would help a lot here rather than havi...

There are uses cases when data input on consolidated level is required and using # is only an additional step for end-user. PALO.DATA function should have an optional argument that would enable inputs on consolidated levels without using #.

When a view is zero suppressed on a large cube, the element Selectors in the Title (POV) dimensions automatically select "Hide Empty Elements" . There is no way to uncheck this without triggering a view refresh in the pasted view. The dialog shoul...

I want to start PDF Batches or Excel Batches after a successfull Integrator job (conditional job). Only if the necessary data was created during an ETL it would be quite convenient to start this PDF Batches from the integrator job as a last step –...

The dropdown list in the 'Project' box is not wide enough to display the full project names. This limitation can pose challenges for users in identifying the correct project to choose, especially for a long project name; for example, a project...

Wenn performing a load of a cube with drillthrough parallel load a log line states : Number of rows in table "<schema>"."table" changed from xxx to yyy the query performed to do that is select count(*) from <schema>.<table> thus ...

For example, After performing 2023-12 consolidation, users should be able to lock all data relating to Actual version and any data 2023-12 and before such that nothing gets changed. current issue: Numbers get changed easily as there is no data loc...