Jedox Ideas

Let us know how we can make Jedox even better!

ADD A NEW IDEA

In-Memory DB

Showing 110

Paging in elements of a dimension

The paging icon appeared when expanding large dimensions in past versions, it could be helpful to enable back this functionality as it is very time consuming when expanding such dimensions and checking each element without the paging in the newer ...
over 3 years ago in Jedox Platform / In-Memory DB 1 Not Planned

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...
12 months 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 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) ...
about 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...
about 1 year ago in Jedox Platform / In-Memory DB 0 Future consideration

Define a separate cube data value for dynarange filtering and sorting

With a dynarange, you can only filter based on the value used for data filtering. If you have e.g. Projects as a vertical dynarange and turnover and costs as a horizontal dynarange, and want to filter out elements where both are 0, you cannot then...
about 5 years ago in Jedox Platform / In-Memory DB 0 Not Planned

Chain splashing calls

make possible to chain splashing commands, such as: copy Budget | ##2000 right now you have to use a macro for that or input both calls
over 4 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 1 year ago in Jedox Platform / In-Memory DB / Jedox Web Navigation 1 Future consideration

History of hierarchy and consolidation factors (weights)

A possibility to set consolidation factors depending of several dimensions would dramatically increase the slowly changing dimensions (SCD, see Kimball's bibles) management possibility of Jedox OLAP server. Example: in 2014 is my Regions hierarch...
about 5 years ago in Jedox Platform / In-Memory DB 0 Future consideration

Standard or Default Element for Splashing

It would be nice to be able to define an element in an hierarchy as standard element. This would mean that when splashing on the parent the full value would be written on this element rather than splashed onto all the underlying elements. This wou...
about 5 years ago in Jedox Platform / In-Memory DB / Jedox Web Navigation / Views 1 Future consideration