Skip to Main Content
Jedox Ideas

Let us know how we can make Jedox even better!

ADD A NEW IDEA

Clear

Ideas

Showing 154

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...
about 2 years ago in Jedox Platform / In-Memory DB 1 Future Consideration

HR - ETL based Social Insurance Calculation

Due to performance issues with rules we would like to have the social insurance calculation based on an ETL / Integrator process. When planning the HR costs and clicking on the button an integrator process should recalculate the social insurances.
about 1 month ago in Jedox Solutions / Human Resources 0 Future Consideration

Configurable Transaction Type Mapping in Balance Sheet Projection

Description Currently, in the balance sheet projection, all values are mapped to two fixed transaction types: Increase and Decrease. This behavior is hardcoded and cannot be adjusted during the mapping process. Proposed Enhancement Introduce the a...
2 months ago in Jedox Solutions / Integrated Financial Planning 0 Future Consideration

Security mechanism to avoid system crashes

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

Align acceptable characters across the platform

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

Improve Jedox robustness: multiple OLAP server

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

Holds need to be easier to see

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...
over 1 year ago in Jedox Platform / In-Memory DB / Planning & Analytics 0 Future Consideration

Dynatable directly from a Cube

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

Minimise customer impact on customizations while upgrading, repairing, updating or changing the models (Eg: Financial Consolidation)

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

Trace Cell allows jump to Rules Editor

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 ...
over 2 years ago in Jedox Platform / In-Memory DB / Jedox Web Navigation / Web Spreadsheet 2 Future Consideration