Ideas

Provide a download/export capability for journal entries (Excel/CSV) to support offline review and reconciliation.

If I configure persisted drill-through in a cube, and in a report select Drill-through, then Jedox shows detailed data from PostgreSQL database. This is great in case of Actual data with detailed information. But in the same time the budget versio...

We have clients who archive previous databases from prior years (but these are still saved on the Jedox server so they can access the database if needed). By default, Jedox loads all databases into memory at server startup. This means the inactive...

Partner feedback: Jedox should provide a standard IFRS 16 leasing template within the EPM platform, rather than relying on partner-built custom solutions.

Such a function is standard for all other Reporting Tools. You only state a start and enddate and the all data in between are selected. With that functionality Jedox would reach another level of usability. Working with the reports would be much m...

There is documentation on what acceptable characters are in Jedox web, Integrator, OLAP. However, this is not enforced by the interface. The Interface should only accept characters that the whole platform can use and enforce these rules.

Today, the robustness of Jedox is often seen as a weak point. If the OLAP database is overloaded by a user launching a view that is ‘too’ complex, or executing an ETL flow that extracts too much data, this disrupts all the other users, including t...

Triggering a cube extract with a lot of rule-based values inside of it leads to a platform crash (in-memory DB exceedes max amount). A mechanism the stops the action instead of letting the action crash the system would be great. The platform shoul...

Allow configurable decimal precision for journal entries to meet client requirements that require greater precision.

Support both division and multiplication methods for flexibility across implementations.