Skip to Main Content
Jedox Ideas

Let us know how we can make Jedox even better!

ADD A NEW IDEA

In-Memory DB

Showing 127

Better calculation stack when tracing a rule calculated cell with overlapping rules

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

Transpose (interchange) rows and columns in the dimension editor of the Modeler

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

Expand Default value of attributes to further components of the Jedox plattform

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

Expand Domain constraints for attributes to further components of the Jedox plattform

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

Allow multiple elements (array) in subset hierarchy filter

Currently it is possible to use multiple hierarchy filters in a subset formula to present multiple hierarchies (e.g. show two of 4 nodes from second level in a dimension). If the hierarchy filter instead would allow for an array of elements, this ...
over 3 years ago in Jedox Platform / In-Memory DB / Jedox Web Navigation 0 Planned

Use Version Type instead of Version Name for Rule Template KPI calculation (by Version)

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

Keep full trace in audit trail.

When planning functions such as splashing or copy are used, the audit trail does not keep a complete record of what has been entered. For example, executing the following command “copy Actual;2023” only records the following NUMERIC_VALUE: 12345,...
11 months ago in Jedox Platform / In-Memory DB 0 Future Consideration

PALO.DATA.SOURCE Identify Rule-based values/cells

PALO.DATA.SOURCE Identify rule-based values/cells Function to identify, if a value is calculated or stored in the database. This enables dynamic reports where a conditional formatting opens cells for data entry ONLY if they are actually stored an...

Active by default - option "Allow multiple parents with a single hierarchy" in Dimension upload wizard"

It can be less dangerous to set the option "Allow multiple parents with a single hierarchy" active by default when elements are uploaded to the dimension. We have encountered several issues when hierarchies with multuple parents were destroyed, be...
about 1 year ago in Jedox Platform / In-Memory DB 1 Future Consideration

Perform complex consolidation logics with more dimensions (14-17)

What it is: Scale performance, while having more dimensions in the database/ cube. Challenge: While having more dimensions (14-17) to the cube, runtime for complex logics, especially consolidation rules are timing out. Use Case: Matrix Consolidati...
about 1 year ago in Jedox Platform / In-Memory DB 0 Future Consideration