Ideas

If you build reports using subsets and the picklist option in the subset editor, and then make a change to the subset in Modeller, the reports do not update without opening each report and resaving. If you have many reports that use the same subse...

Comboboxes (or more generic buttons) sometimes have actions. It can be very inconvenient or even frustrating, if you forget about automation, which is bound to these components. Often you also simply copy an existing report/ canvas and continue to...

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...

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...

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 #.

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.

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...

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...