Ideas

The current REST Connector only supports one connection setup from JEDOX -> Server. This means that each accessing server must first open an incoming port. When an incoming port is opened, further steps must be initiated to secure the server. T...

Buttons in "Posting Journal Entry" move to the top instead of having them at bottom. Because if there are many JEs to be posted, the user need to scroll all the way to the bottom, but the step before of selecting All JEs is at the top. Sometimes t...

As Jedox has more and more data visualisations functionality, instead of developing your own graph, there are a lot of providers opensource-licenced that a jedox user could use as a data visualisation. Olap cubes, as they are a "rigid" structures,...

It would be good to have more MicroCharts to design Dashboards and Reports. Especially horizontal bar charts (Variance Charts) would be nice. I use them all the time to indicate positive or negative variances. In Excel they are made with conditi...

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

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

Offering a native DuckDB connector first would give Jedox a commercial advantage with data-driven teams and pave the way for scalability via MotherDuck without changing the API.

it could be usefull to have a new log level "Info+" : sometimes it is useful to log informations that are relevant and that you want to catch attention to, but you do not want to cause a warning. A new method "LOG.infoPlus()" or something would be...