Jedox Ideas

Let us know how we can make Jedox even better!

ADD A NEW IDEA

In-Memory DB

Showing 120

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

Improve server performance with Configuration Option to Disable Loading Inactive Databases on server startup

We have clients who archive previous databases from prior years (but these are still saved on the Jedox server so they can access the database if needed). By default, Jedox loads all databases into memory at server startup. This means the inactive...
4 months ago in Jedox Platform / In-Memory DB 1 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...
9 months ago in Jedox Platform / In-Memory DB 1 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...
3 months ago in Jedox Platform / In-Memory DB / Planning & Analytics 0 Future Consideration

Sort Rules of a cube with Drag and Drop

We are using various rules and sometimes they have to be properly sorted afterwards. It would make the handling easier, if the rules can be sorted via drag and drop option rather than having to click 15 times on the sort arrow on the right side. I...
28 days 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.
9 months ago in Jedox Platform / In-Memory DB 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...
about 2 months ago in Jedox Platform / In-Memory DB 0 Future Consideration

Delete Cube Button before Clear Cube Button

I wonder if the Delete Cube button can be moved to the far right, making it the last button accessible. Recently, I accidentally pressed the Delete button instead of the Clear button and ended up losing all my day’s work. This was incredibly frust...
about 1 month ago in Jedox Platform / In-Memory DB 0 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...
over 1 year ago in Jedox Platform / In-Memory DB 1 Future Consideration

Splasher to write into first base child of the element

It will be good to have a splasher option to writeback at the first base element of each parent element. This will save the cube filled up with too much data. Sometimes it is necessary to allow writeback at total level but it is not good to splash...
about 1 month ago in Jedox Platform / In-Memory DB / Planning & Analytics 0 Future Consideration