My 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 have a customer who is very happy with the drill through functionality in Jedox. It pulls out all the transactions that makes up the number in the cube cell but it doesn't show the sum of all the lines. Is is possible to add the total or have i...

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

Hi, I have found that Copy paste functionality in macro editor in jedox web doesn't interact with Clipboard, this means we cannot copy the code into notepad and edit it outside the macro editor. There are buttons for copy and paste but they don't ...

It could be great to change some link in the login Page. Especially the contact. Because, the final user who came to have an access, a question or to report a problem without having an access will click on the "contact link" and send mail to jedox...

It would be great, if there is a possibility to hide the Model Icon in the top toolbar. We don’t use the models and our users are confused with a button to a white page.

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