Ideas

Introduce a native Jedox connector for Xero, enabling connection and extraction of key financial data like Trial Balance, Aged Payables, Journals, and other standard reports. Encryption and OAuth 2.0 authentication to comply with Xero's security s...

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

With the current Canva functionality, it is not possible use horizontal scrollbar all the time, it gets active only when you go to the bottom of the report. I find it difficult to use Canva reports when I have a horizontal dynarange and the only p...

Currently one has to create a conditional formatting to implement alternating row colors. As soon as rows are dynamically hidden or extended (e.g. drill-down in DynaRange), the alternating row colors are broken. Just like the frame of the DynaRang...

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

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.