Ideas

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

As a Word user working on disclosure reporting in ESG (Environmental, Social, and Governance) or Legal Consolidation, I want the ability to insert specific Jedox data and reports directly into my document. This means I need a feature that allows m...

The emerging trend of content-specific chatbots has the potential to significantly boost the usage of the Jedox knowledge base. By simply uploading relevant documents, you can fine-tune an existing LLM model to focus on specific topics. If the kno...

In the old/legacy add-in you had the functionality that you can use a variable manager for adding or using existing variables by editing the paste view and select elements. Please implement the variable function for the JOA add-in as well. Due to ...

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

Today, administrators need access to Jedox SFTP server to upload large files. This is also true for uploading large database backups. File Designer does not allow to upload large files (see idea https://feedback.jedox.com/ideas/JS-I-1643). In ...

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

When you have data in more than one cube, asking AI to leverage more than one cube to bring back a result is the ultimate AI concept. It would require the AI to be able to understand relations in the data and perhaps prompt with a clarification qu...

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