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 #.
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...
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...
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...
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...
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.
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...
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...
In Modeller group databases by model to which they belong.
In Modeler we often have many databases with different names. In our situation, we have several teams working on separate projects.Most projects are grouped via Models functionality where the Model groups Reports, Integrator jobs, and Scheduler ta...
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...