Skip to Main Content
Jedox Ideas

Let us know how we can make Jedox even better!

ADD A NEW IDEA

Clear

In-Memory DB

Undo should be more userfriendly. Active by default. Reset when user session ends.

Undo should be more userfriendly. Active by default. Reset when user session ends.
13 days ago in Jedox Platform / In-Memory DB 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...
over 2 years ago in Jedox Platform / In-Memory DB 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.
over 2 years ago in Jedox Platform / In-Memory DB Future Consideration

Rule Editor - moving many rules directly to position xx

Actually it is only possible to move a single rule up or down line by line which is extremely annoying when I need to move a few rules by many lines.Proposal is to select multiple rules and have the option to "move to position no. xx"
about 2 months ago in Jedox Platform / In-Memory DB Future Consideration

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...
almost 2 years ago in Jedox Platform / In-Memory DB Future Consideration

Improve Jedox robustness: multiple OLAP server

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...
over 1 year ago in Jedox Platform / In-Memory DB Future Consideration

Trace Cell allows jump to Rules Editor

The Trace Cell is a great feature, but to make it even better let's add the capability to jump from there to the active rule so we can debug and edit it as necessary. Often you can get lost in the weeds and being able to jump directly to the Rule ...
almost 3 years ago in Jedox Platform / In-Memory DB / Jedox Web Navigation / Web Spreadsheet Future Consideration

Make license type name available in cube

Currently, #_USER_USER_PROPERTIES cube only shows the license code ID. There is also #_LICENSE cube but there are no licenses in it. The request is for license type names (feature set within the license code) to be available in a cube, so that a p...
6 months ago in Jedox Platform / In-Memory DB 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...
almost 2 years ago in Jedox Platform / In-Memory DB / Planning & Analytics 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 3 years ago in Jedox Platform / In-Memory DB Future Consideration