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"...
Challenge: Currently users are allowed to save/ post data to the closed periods. Eg: 2022.Dec, financial report is approved and published. Users are not supposed to alter/ change this data. However, currently in Jedox it is possible.
We are using various rules and sometimes they have to be properly sorted afterwards. It would make the handling easier, if the rules can be sorted via drag and drop option rather than having to click 15 times on the sort arrow on the right side. I...
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 ...
Csv files used to be important in database downloads for compatibility between Windows and Linux in on-premise environments. Since we are two years past the transition to cloud-only, this is no longer necessary in most cases, as downloaded databas...
From https://knowledgebase.jedox.com/jedox/in-memory-db/rule-templates-query-types.htm, Actual Months rule template, "If fiscal year is used, it returns a list of the first months of each fiscal year." The partner wants the rule template to give t...
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,
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 #.
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...
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...
