Skip to Main Content
Jedox Ideas

Let us know how we can make Jedox even better!

ADD A NEW IDEA

In-Memory DB

Showing 121

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

Rule Editor usability/GUI - grouping in folders

The rule editor is very powerful but hard to understand from a business user point of view. The user interface could be improved in terms of usability and structure. A grouping of rules in a folder structure would help a lot here rather than havi...
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...
4 months ago in Jedox Platform / In-Memory DB 0 Future Consideration

OLAP access restrictions

Currently, cloud console users can create security rules that restrict inbound traffic, allowing connections only for the specified IP addresses or IP ranges (IP whitelisting). See also: https://knowledgebase.jedox.com/jedox/maintenance/cloud-cons...
8 months ago in Jedox Platform / Cloud Console & Administration / In-Memory DB 0 Already exists

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

Splashing for string elements

Possibility to splash a string to aggregated cell so every base cell will have the same string afterwards. Practically this would mean adding support for splashing strings via splash operation ! and also adding support for copy operation with stri...
over 5 years ago in Jedox Platform / In-Memory DB 1 Not Planned

Cancel / Abort Calculation in Jedox Web V2

Unfortunately there was no official statement to my comment on topic http://feedback.jedox.com/forums/220460-jedox-feature-voting-tool?query=cancel Thats why I opened the same feature reqest again. The main problem is, that during calculations...
over 5 years ago in Jedox Platform / In-Memory DB / Jedox Web Navigation 1 Future Consideration

Automatically update Olap Lists when a dimension name is changed

Currently, when renaming a dimension, a List where this dimension is used isn't automatically updated, and then has to be manually recreated. It would be nice if this could be done automatically whenever a dimension name is changed.
9 months 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...