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

Thank you for adding buttons to the native canvas components. Great archievement. Here an idea to add even more value: as an implementation expert I have to style each button in every canvas report. It would be more beneficial to define one or thr...

While using DynaTables in Canvas, it would be useful to allow the end-user to directly open the DynaTable in a full view including the POV selection. Could either be an "Expand" button on the DynaTable used in Canvas, or a way to hyperlink to a sp...

In 99% of creating a combobox we setup a subset. Currently the default is always "Simple Data Source". Please adjust it to "Subset". View screenshots.

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.

It will be very useful to have an option to create a Dynatable directly from Modeler->Database->Cube. It will take less time to understand what values the cube has.

It's necessary to add Trace Cell Value to be able to debug the values.

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.

There should be an option in the Dynarange editor to hide the involved rows if the (vertical) dynarange returns no result. This is especially valid for nested Dynaranges. Right now it is always additional effort to simulate this via HIDEROW func...

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