Ideas

Integrator: Enable writeback via load for JDBC connections Users expect that writeback is also supported by JDBC connections.

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

Please adjust the dimension structure upload for the dimensions: PnL, BS, CC and all other dimensions which have the same case: Currently I download an empty excel file and upload it. If I click on download again the excel file is again empty. I c...

It would be amazing to see a data preview on cubes in the modeler like a tabular view in the integrator with data preview and max rows. For testing and debuging I would really often use this - but now I have to download the cube each time if I wan...

Based on the existing, broken demo example, it would be great to have such an output, customers are asking for. It shows, how we can structure the content overview in a quantitative and qualitative way, basically iterating through the whole conten...

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

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.