Skip to Main Content
Jedox Ideas

Let us know how we can make Jedox even better!

ADD A NEW IDEA

In-Memory DB

Showing 112

Security mechanism to avoid system crashes

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...
5 days ago in Jedox Platform / In-Memory DB 0 Future consideration

Improve server performance with Configuration Option to Disable Loading Inactive Databases on server startup

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...
2 months ago in Jedox Platform / In-Memory DB 1 Future consideration

Data Filter, extended zero suppression.

It would be very helpful to have the following filter option in the subset data filter. A filter option that displays all parent elements as soon as at least one child element has a value, even if the parent elements themselves are zero. (please s...
5 days ago in Jedox Platform / In-Memory DB / Planning & Analytics 0 Future consideration

Holds need to be easier to see

It would be very useful to have an icon or other indication which cells are being held with a Hold Statement. Currently Doohickey's/Dept 1 is being held (highlighted in Yellow), but there is not a way to determine that from visually looking. Worse...
about 2 months ago in Jedox Platform / In-Memory DB / Planning & Analytics 0 Future consideration

Drill-through from a Jedox cube if no data in a PostgreSQL database

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...
8 months ago in Jedox Platform / In-Memory DB 0 Future consideration

To enable users to lock data at month and version dimension for fincon model

For example, After performing 2023-12 consolidation, users should be able to lock all data relating to Actual version and any data 2023-12 and before such that nothing gets changed. current issue: Numbers get changed easily as there is no data loc...
about 1 month ago in Jedox Platform / In-Memory DB 0 Future consideration

Align acceptable characters across the platform

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.
8 months ago in Jedox Platform / In-Memory DB 0 Future consideration

Data Locking

Challenge: Currently users are allowed to save/ post data to the closed periods. Eg: 2022.Dec, financial report is approved and published. Users are not supposed to alter/ change this data. However, currently in Jedox it is possible.
about 1 month ago in Jedox Platform / In-Memory DB / Planning & Analytics 0 Future consideration

Modification for Actual Months rule template

From https://knowledgebase.jedox.com/jedox/in-memory-db/rule-templates-query-types.htm, Actual Months rule template, "If fiscal year is used, it returns a list of the first months of each fiscal year." The partner wants the rule template to give t...
about 2 months ago in Jedox Platform / In-Memory DB 0 Future consideration

Minimise customer impact on customizations while upgrading, repairing, updating or changing the models (Eg: Financial Consolidation)

Customer Challenge: Currently, all items in Reports, Report Designer, Tasks and Integrator are removed before being replaced by the (new) content from the model packages. As a result customer/ consultants do not want to upgrade their existing work...
over 1 year ago in Jedox Platform / In-Memory DB 1 Future consideration