Jedox Platform

A PALO.DATA function refers to single base or consolidated elements for aggregation. It would be fine to be able to define subsets of elements to get a sum of these,

The rule editor is very powerful but hard to understand from a business user point of view. The user interface could be improved in terms of usability and structure. A grouping of rules in a folder structure would help a lot here rather than havi...

There are uses cases when data input on consolidated level is required and using # is only an additional step for end-user. PALO.DATA function should have an optional argument that would enable inputs on consolidated levels without using #.

I want to execute an action from an hyperlink formula to delete an element and add an "Are you sure" message. I could do this with an action, but as I cannot execute actions from the hyperlink formula I have to create an additional report with the...

Goal: Show error message to the end-user without any action. Example: users can currently click on a button and execute an ETL job without selecting the correct (base) elements in the comboboxes (e.g., choosing "All cost centers" is not allowed). ...

Dark mode like in Excel

I want to restrict e.g. PALO.EL formulars for all my platform users as performance suffers from its usage. The function "Ignore order of arguments" in the individual setting section would allow for this on an individual level. But I cannot check t...

Dynaranges seem to be a key functionality of Jedox, but their functionality is surprisingly limited when it comes to conditional formatting. It would be ideal if adjustments were made so that conditional formatting could correctly apply to interac...

Allow Native Jedox user accounts to be setup with two factor authentication.

Whilst you need to ensure that there is always at least 1 account that is a member of the Admin role (via a group), it does not need to be the default Admin user account that is shipped with the product. The issue is that this is a basic authentic...