Ideas

The Jedox Knowledgebase is a helpful treasure chest of knowledge in my daily work. However, I do see room for optimization: 1. due to the size of the knowledgebase, searching for a topic always results in a large number of hits. This could be coun...

A clustered and stacked chart has clusters of columns or bars, with a stack in each column or bar. Similar to the example shown below: This type of chart can be used to compare actual vs. budget by category, for example.

Before moving to Jedox, we used the Cockpit from Cubeware.This Frontend provided a possibilty to debug the starttime of a given report. The debug window showed every step of the loading-procedure of a report. Why would this be helpful in Jedox?I h...

Option to set criteria to enable/disbale user controls (perhaps similar to how you can currently show or hide these). The issue with the current functionality is that users are either able to interact with a user control (such as a workflow submis...

It would be great to add an Autofilter simular to Excel onto a spreadsheet (onto a dynarange). Current situation: All filters in a Jedox Web spreadsheet have to be implemented manually one by one via dropdowns, subsets etc. This is great to...

All colour codes, fill/border, line formats and positioning on charts should be able to be passed in from a range, named range or variable. This would essentially bring a basic "conditional" formatting to charts and cover the main things the users...

Whit large implementations, where many hierarchies and cubes exists, a lot of time is spent on finding and scrolling to the hierarchies related to the cube being worked on. Although the forward and back buttons help a lot, it would also be great t...

The suggestion is to add the following two languages as supported by Jedox Web: Polish (pl-PL) Slovak (sk_SK) This should allow the user to change the language of the UI - Jedox Web as well as to use it to translate elements/attributes/reporting i...

I'd like it if, when the user clicks on a button, that same button could keep its properties (background, font, etc.) and not be displayed again by default. A bit like checkboxes that keep the tick displayed when you click on them.

Cube-to-Cube drillthrough would allow cubes to be linked logically for users and assist in data discovery. The drillthrough would use the shared dimensions for a particular drillthrough intersection to create a view on the destination cube.