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

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

It could be great to change some link in the login Page. Especially the contact. Because, the final user who came to have an access, a question or to report a problem without having an access will click on the "contact link" and send mail to jedox...

It would be great, if there is a possibility to hide the Model Icon in the top toolbar. We don’t use the models and our users are confused with a button to a white page.

Whilst you need to ensure that there is always at least 1 account that is a member of the Admin role (via a group), it does not need to be the default Admin user account that is shipped with the product. The issue is that this is a basic authentic...

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.