Adding a description field to the Database would allow better documentation of the type of data in the database. Dimension and Cube descriptors are helpful, and this would enhance the documentation. Tags would also be useful (like Dimension "Type"...
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 ...
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...
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...
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...
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...
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.
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...
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 #.
Aggregate lists of elements for each dimension in PALO.DATA functions instead of single.
A PALO.DATA function refers to single base or consolidated elements for aggregation. It would be fine to be able to define subsets of elements to get a sum of these,