Jedox Ideas

Let us know how we can make Jedox even better!

ADD A NEW IDEA

In-Memory DB

Showing 127 of 1335

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

Duplicate Databases

In order to create a backup of a database one has to download and the upload the database. This should be possible with one step only. Like the duplicate function for Integrator projects.
4 months ago in Jedox Platform / In-Memory DB 2 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...
7 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...
8 months 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 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...
9 months ago in Jedox Platform / In-Memory DB / Planning & Analytics 0 Future Consideration

Choose Timerange by DatePicker

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...
almost 6 years ago in Jedox Platform / In-Memory DB / Jedox Web Navigation 3 Not Planned