Jedox Ideas

Let us know how we can make Jedox even better!

ADD A NEW IDEA

In-Memory DB

Showing 129 of 1395

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...
about 2 years ago in Jedox Platform / In-Memory DB 0 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...
about 1 year ago in Jedox Platform / In-Memory DB / Planning & Analytics 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...
over 6 years ago in Jedox Platform / In-Memory DB / Jedox Web Navigation / Microsoft Office integrations (Excel, PowerPoint, & Word) 1 Future Consideration

SVS new Parameter for sep_error needed to show warnings or info messages without cancelling the writeback

Situation: we would like to inform the users about specific input fields and value combinations to be informed about possible mistake (value sign wrong or wrong range). sep_error(title,msg); Allthough the value has been written to the cube prior t...
about 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 &...
about 2 years 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) ...
about 2 years 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...
about 2 years ago in Jedox Platform / In-Memory DB 0 Future Consideration

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

In a cube with persisted relational ETL drillthrough data, allow cube-drilldown in areas where no relational data is available.

As of version 2023.4, the Jedox drillthrough capabilities have become a native functionality outside of the SVS scripts. In the KB it says for the mode automatic: drills through if ETL is available, or else drills down. This suggest that right-cli...
about 1 year ago in Jedox Platform / In-Memory DB 0 Future Consideration

LET Function in rules

a LET function would be really helpful in the rules, especially for complex ones.
over 4 years ago in Jedox Platform / In-Memory DB 0 Future Consideration