Ideas

There is documentation on what acceptable characters are in Jedox web, Integrator, OLAP. However, this is not enforced by the interface. The Interface should only accept characters that the whole platform can use and enforce these rules.

Today, the robustness of Jedox is often seen as a weak point. If the OLAP database is overloaded by a user launching a view that is ‘too’ complex, or executing an ETL flow that extracts too much data, this disrupts all the other users, including t...

Triggering a cube extract with a lot of rule-based values inside of it leads to a platform crash (in-memory DB exceedes max amount). A mechanism the stops the action instead of letting the action crash the system would be great. The platform shoul...

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

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

It would be great to record and display in history value that was replaced. Then user will get the overview and it would be easier to go back to previous value. Users won't be afraid to make a mistake, because there will be a way to find out what ...

Currently, in the PALO.DFILTER function, filtering based on a string value is limited to only one specific value at a time (e.g., = "Comment a"). This limitation restricts the ability to filter multiple values or patterns dynamically. It would be ...

The Trace Cell is a great feature, but to make it even better let's add the capability to jump from there to the active rule so we can debug and edit it as necessary. Often you can get lost in the weeds and being able to jump directly to the Rule ...

Customer Challenge: Currently, all items in Reports, Report Designer, Tasks and Integrator are removed before being replaced by the (new) content from the model packages. As a result customer/ consultants do not want to upgrade their existing work...

It should be possible to preselect the alias as the default value to avoid confusing users with IDs defined as base elements. The setting should be made user-specific.