In-Memory DB

In complex planning situations, separate rules calculating identical cube areas are required, using CONTINUE and STET statements. This has the advantage of separating out logic branches to make calculations easier to read in the Rules Editor in Mo...

Everything is in the title, but for some specification here's the complete idea : What ? Add an attribute "Category" or "TimeType" that categorize element in the dimension. So for element like : 2022-01-01 or 2023-05-01 the attribute should have t...

Some dimension have more attributes then elements. In these cases it would help to transpose/ interchange between columns & rows in order to make more values fit on one page. Having e.g. all values on one screen would help to get a faster &...

The functionality to set Default values for dimension element attributes (currently available in the Modeler) should be also available a) when uploading a dimension from a file with the Modeler, b) when loading a dimension with Integrator, c) ...

The functionality to constraint attribute values via a Domain (currently available in the Modeler) should be also available a) when uploading a dimension from a file with the Modeler, b) when loading a dimension with Integrator, c) when enteri...

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

Possibility to select application area of attribute filter - all/consolidated/base. UseCases: Only Base: for combobox, dynarange - display complete hierarchy, but base elements under consolidations are displayed based on attribute filter. Only Con...

From https://knowledgebase.jedox.com/jedox/in-memory-db/rule-templates-query-types.htm, section KPI calculation (by Version), there was a note that "for this query type, the version dimension must have the specific name "Version". This naming requ...

Hi, I suggest a new splashing command: copy without overwriting values not equal 0/null in target E.g., when updating a forecast version with actual values BR Axel

Having the ability to customize spread commands based off of a clients choosing (i.e. 4-4-5, 4-5-4, 5-4-4, or custom)? This is highly important to clients using 4-4-5 calendar in Manufacturing, health, etc. It would be nice if you could set how th...