Jedox Ideas

Let us know how we can make Jedox even better!

ADD A NEW IDEA

Search results: In-Memory DB

Showing 11

Visual Flow and Debugging Tool for Jedox Business Rules

Business rules in Jedox are inherently complex to define and even harder to understand, debug and test. It is difficult to trace the exact execution order, sorting/ordering dependencies and the end-to-end calculation flow, and to determine which m...
15 days ago in Jedox Platform / In-Memory DB 0 Future Consideration

Drill-through from a Jedox cube if no data in a PostgreSQL database

If I configure persisted drill-through in a cube, and in a report select Drill-through, then Jedox shows detailed data from PostgreSQL database. This is great in case of Actual data with detailed information. But in the same time the budget versio...
over 1 year ago in Jedox Platform / In-Memory DB 1 Future Consideration

Enable Rolling Forecast Periods to Include Future Months

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 ...
3 months ago in Jedox Platform / In-Memory DB 0 Future Consideration

Flexible String Filtering in PALO.DFILTER (Multi-Select or Regex)

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 ...
6 months ago in Jedox Platform / In-Memory DB 0 Future Consideration

Palo.data.Min / Max / Avg in Rule

I need from a data cube the minimum and maximum value for selected elements. With Palo.data.Min and .Max formula you can find out the value for a single selection, but I need this in a separate cube to work on with the result. Please add the Palo....
7 months ago in Jedox Platform / In-Memory DB 0 Future Consideration

Use Version Type instead of Version Name for Rule Template KPI calculation (by Version)

From https://knowledgebase.jedox.com/jedox/in-memory-db/rule-templates-query-types.htm, section KPI calculation (by Version), there was a note that "for this query type, the version dimension must have the specific name "Version". This naming requ...
about 2 years ago in Jedox Platform / In-Memory DB / Jedox Web Navigation 1 Future Consideration

Filter virtual dimension elements in Views / Charts

A virtual dimension always has a certain structure. - <attribute name>-- Total <attribute name>--- <attribute value>---- <base element>-- No <attribute name>--- <base element> While this is good enough for data ...
almost 2 years ago in Jedox Platform / In-Memory DB / Views 0 Future Consideration

Attribute "Name" should be shown for multiple languages by default

In Modeler in dimension attribut e.g. "Name" should be shown for multiple languages by default or based on selection & activate search functionality. Use case: Currently as a user I need to select each time I open the dimension the Name German...
almost 4 years ago in Jedox Platform / In-Memory DB 0 Future Consideration

subset: attribute filter - select area of application to all/consolidated/base

Possibility to select application area of attribute filter - all/consolidated/base. UseCases: Only Base: for combobox, dynarange - display complete hierarchy, but base elements under consolidations are displayed based on attribute filter. Only Con...
about 2 years ago in Jedox Platform / In-Memory DB 0 Future Consideration

Too Big Splash Warning incorrectly focuses Planning Assistant on "Like" not "Splash"

When you attempt a number that impacts many cells, Jedox give you a warning that you are potentially impacting more then you intend. It gives you the option through the Planning Assistant to modify it. However, when you delete a large number with ...
over 2 years ago in Jedox Platform / In-Memory DB 0 Future Consideration