Ideas

It would be very useful to have an icon or other indication which cells are being held with a Hold Statement. Currently Doohickey's/Dept 1 is being held (highlighted in Yellow), but there is not a way to determine that from visually looking. Worse...

Overview: Currently, Jedox’s rolling forecasting setup primarily supports historical or past periods, limiting the ability to plan dynamically for future months. To support more agile and forward-looking planning, it is recommended to introduce a ...

There are several known issues/limitations with the current implementation of merged cells: Thick border problem on merged cells If formatted gets white border. Problem with merged cell when scrolling Merged cells and freeze pane Merged ...

For dashboards and data visualisation, our customers are using maps (google, ESRI, OpenStreetMap, etc) as data visualisation tools. For example, if you have a store, and customer dimension, you could have Latitude-longitude attributes, based on wh...

Please add the feature "hide empty elements" for all selections. So if I have a list of products and I select "hide empty elements" it should show me only those with data. So "old products" which I need to keep to compare current data with old dat...

It will be very useful to have an option to create a Dynatable directly from Modeler->Database->Cube. It will take less time to understand what values the cube has.

I would like to show an attribute value in a KPI card. Currently I can only show data cubes and not attribute cubes.

Especially, when a session has expired or the server is temporarily unreachable, and/or the issue is most likely not with Jedox itself! The screenshots' alleged "critical error messages" are reactions to an "expected system behavior". Today, the e...

Currently, a Canvas KPI Card only accepts a specific cube cell as data source (with the ability to multi-select some dimension elements and then use average, min, or max, like in a View). This implies that all data to be shown on a KPI Card must b...

instead of forcing the creation of folders by component type (e.g. "Cube", "Dimension", .. for extracts), it would be very much appreciated, if it was possible to create a folder-structure by user. Potentially, these folders could also span across...