Ideas

Enable drill-down begin of a dynarange not only by "hardcoded" number, but with a variable. So you could easily set up the expansion levels.

There is documentation on what acceptable characters are in Jedox web, Integrator, OLAP. However, this is not enforced by the interface. The Interface should only accept characters that the whole platform can use and enforce these rules.

Today, the robustness of Jedox is often seen as a weak point. If the OLAP database is overloaded by a user launching a view that is ‘too’ complex, or executing an ETL flow that extracts too much data, this disrupts all the other users, including t...

Similar to SAP, a new connection type to DATEV should be offered, ideally with pre-built extract types, to be able to quickly generate master and transactional data in Jedox.

Triggering a cube extract with a lot of rule-based values inside of it leads to a platform crash (in-memory DB exceedes max amount). A mechanism the stops the action instead of letting the action crash the system would be great. The platform shoul...

It would be very useful to have an icon or other indication which cells are being held with a Hold Statement. Currently Doohickey's/Dept 1 is being held (highlighted in Yellow), but there is not a way to determine that from visually looking. Worse...

It would be great to record and display in history value that was replaced. Then user will get the overview and it would be easier to go back to previous value. Users won't be afraid to make a mistake, because there will be a way to find out what ...

Currently, in the PALO.DFILTER function, filtering based on a string value is limited to only one specific value at a time (e.g., = "Comment a"). This limitation restricts the ability to filter multiple values or patterns dynamically. It would be ...

The Trace Cell is a great feature, but to make it even better let's add the capability to jump from there to the active rule so we can debug and edit it as necessary. Often you can get lost in the weeds and being able to jump directly to the Rule ...

instead of forcing the creation of folders by component type (e.g. "Cube", "Dimension", .. for extracts), it would be very much appreciated, if it was possible to create a folder-structure by user. Potentially, these folders could also span across...