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,
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...
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 #.
To enable users to lock data at month and version dimension for fincon model
For example, After performing 2023-12 consolidation, users should be able to lock all data relating to Actual version and any data 2023-12 and before such that nothing gets changed. current issue: Numbers get changed easily as there is no data loc...
When a web report is open, it is not possible to mark/select the shown numbers, thus, it's also not possible to copy them e.g. for a quick check etc. It's also not possible to copy the value in a drillthrough.
In the olap Plan & Forecast App there was a functionality that you could double-tap and then swipe on the starting screen with two fingers and then the logs of the mobile app were displayed. There were additional two buttons to be able to send...
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...
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...