Skip to Main Content
Jedox Ideas

Let us know how we can make Jedox even better!

ADD A NEW IDEA

Clear

In-Memory DB

Showing 130 of 1410

Option to set alias as default value

It should be possible to preselect the alias as the default value to avoid confusing users with IDs defined as base elements. The setting should be made user-specific.

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...
over 6 years ago in Jedox Platform / In-Memory DB 0 Not Planned

combine palo.data and palo.setdata to DISPLAY C-element but write on BASE-element

In planning scenarios a lot of customers demand the ability to adjust values by entering the new total value (often on calculated as a c-element). In order to facilitate this behaviour, you have to significantly increase report complexity. Therefo...
over 6 years ago in Jedox Platform / In-Memory DB 0 Future Consideration

Display No Access to non access elements instead of #Value

When we setup a security at dimension level, some users are set as N to prevent an access. In report spreadsheet, the element is displayed in a single cell (not using dynarange). But when non eligible user open the report, the particular element t...

show explicit right when inherited

in #_GROUP_DIMENSION_ cube this is really complex to know what is the right for a certain group since it can be inherited from upper levels, for instance: Europe N West France R this would be great to be able to see that, say using a "flag" t...
over 6 years ago in Jedox Platform / In-Memory DB / Jedox Web Navigation 0 Future Consideration

Materialized Rules / Persisted Rules - for Performance Optimization (like materialized views)

Currently rules are calculated in the moment when the user queries the data. It would be great to have the option to shift the timing to the point when the user changes data. So the result of the calculation would be stored/persisted when the use...
over 6 years ago in Jedox Platform / In-Memory DB 0 Future Consideration

Attributes / Flags for Rules

Hi Jedox team, currently we only have a comment section to add additional information to a rule. But especially for automated processing of rules via ETL it would be great to be able to mark/flag certain rules in a more structured way. In the fi...
over 6 years ago in Jedox Platform / In-Memory DB 0 Not Planned

Substitute #VALUE errors from missing rights by 0

If a user is restricted by #_GROUP_DIMENSION_DATA_* to a specific area he will usually get a #VALUE error for everything else (in Web as well as Excel). Sometimes it would be more beneficial to treat these #VALUE errors as 0s, so that the user exp...
over 6 years 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...

Rule template on System dimensions

Allow queries on System dimensions, for instance #_GROUP_, to be able to define dynamic right rules (e.g. in #_GROUP_CELL_DATA_)
over 6 years ago in Jedox Platform / In-Memory DB 0 Not Planned