Jedox Ideas

Let us know how we can make Jedox even better!

ADD A NEW IDEA

In-Memory DB

Showing 91

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 2 months ago in Jedox Platform / In-Memory DB / Planning & Analytics 0 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 2 months ago in Jedox Platform / In-Memory DB 0 Future Consideration

Hide all #VALUE errors

Especially on opening or reloading a workbook for a short moment there may be displayed lots of #VALUE errors, while Jedox is retrieving data. Only possibility to hide these currently is an optional formatting for text color to match background co...
over 5 years ago in Jedox Platform / In-Memory DB / Jedox Web Navigation / Microsoft Office integrations (Excel, PowerPoint, & Word) 1 Future Consideration

Semi-additive measures: AverageNonEmpty, LastNonEmpty

It is very helpful that Jedox has implemented the first semi-additive measures in version 6. (AVG, Last/First Child) It would be great if this could be continued by 2 more of them: 1.) Most important would be AverageNonEmpty, to get an avarage o...
over 5 years ago in Jedox Platform / In-Memory DB 3 Future Consideration

Drillthrough decimal symbol same as on screen/report

Decimal symbols are currently linked to the user-locale. English setting will give a dot (.) as decimal symbol whereas the Dutch setting, for example, will give a comma (,) This feature works on the screens/reports, but this does not happen with ...
over 5 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...
3 months ago in Jedox Platform / In-Memory DB 0 Future Consideration

Allow the Admin user account to be removed or deactivated in Jedox suite

Whilst you need to ensure that there is always at least 1 account that is a member of the Admin role (via a group), it does not need to be the default Admin user account that is shipped with the product. The issue is that this is a basic authentic...
almost 3 years ago in Jedox Platform / In-Memory DB 1 Future Consideration

Additional argument in PALO.DATA function to omit hashtag (#) sign for data splashing

There are uses cases when data input on consolidated level is required and using # is only an additional step for end-user. PALO.DATA function should have an optional argument that would enable inputs on consolidated levels without using #.
over 5 years ago in Jedox Platform / In-Memory DB 0 Future Consideration

Fix first column in Dimension Editor in Modeller

Whe you have a lot of attributes in an dimension, you always have to scroll to the right to maintain all attributes. But as the first column (element name) is not fixed, the element names get out of the screen. So you always loose the link between...
almost 3 years ago in Jedox Platform / In-Memory DB 0 Future Consideration

Create alias for dimension name

For models, some dimension names come as part of the model and the dimension name shouldn't be changed. Therefore the request is for a platform functionality for dimensions to also have aliases, so that the dimension can be referred to by its alia...
8 months ago in Jedox Platform / In-Memory DB 0 Future Consideration