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

Such a function is standard for all other Reporting Tools. You only state a start and enddate and the all data in between are selected. With that functionality Jedox would reach another level of usability. Working with the reports would be much m...

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

Allow users to display dimensions as a flat list (without hierarchy) in the Rows area of a View in the Excel Add-in. Not all reports require the full hierarchical structure, and having a flat view can simplify reporting and improve readability fo...

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

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

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