My ideas: In-Memory DB

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

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"

In the modeler, if I select a cube or dimension, I would like to see where in my application they are used: In which workbook In which ETL step In which rule etc Currently, this is quite a manual exercise and practically impossible to gras...

this would be really helpful to have a locking mechanism when creating elements. The use case is the following: Application where users can create new elements (e.g. Capex or Projects), for instance using a macro or actions The elements should...

It would be highly beneficial to include a MIN/MAX function for semi-additive measures, as there is currently no alternative that is both performant, easy to maintain, and capable of reacting dynamically to changes in data. I’ve encountered this n...

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

Currently there are two options when you click on the "Export" button in the rules area of a cube: 1) Database Script / 2) Text File. It looks like these are two options for the same outcome. But actually it's not: 2) extracts the rules only / 1) ...

Business rules in Jedox are inherently complex to define and even harder to understand, debug and test. It is difficult to trace the exact execution order, sorting/ordering dependencies and the end-to-end calculation flow, and to determine which m...

Overview: Currently, Jedox’s rolling forecasting setup primarily supports historical or past periods, limiting the ability to plan dynamically for future months. To support more agile and forward-looking planning, it is recommended to introduce a ...

Currently, in the PALO.DFILTER function, filtering based on a string value is limited to only one specific value at a time (e.g., = "Comment a"). This limitation restricts the ability to filter multiple values or patterns dynamically. It would be ...