Skip to Main Content
Jedox Ideas

Let us know how we can make Jedox even better!

ADD A NEW IDEA

Clear

Ideas

Showing 285

Aggregate lists of elements for each dimension in PALO.DATA functions instead of single.

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,
over 6 years ago in Jedox Platform / In-Memory DB 3 Future Consideration

Rule Editor usability/GUI - grouping in folders

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

Additional argument in PALO.DATA function to omit hashtag (#) sign for data splashing

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

Start Scheduled Tasks from Integrator (Batch PDF, etc)

I want to start PDF Batches or Excel Batches after a successfull Integrator job (conditional job). Only if the necessary data was created during an ETL it would be quite convenient to start this PDF Batches from the integrator job as a last step –...
over 3 years ago in Jedox Platform / Integrator 0 Future Consideration

Option to deactivate logging of updated rows

Wenn performing a load of a cube with drillthrough parallel load a log line states : Number of rows in table "<schema>"."table" changed from xxx to yyy the query performed to do that is select count(*) from <schema>.<table> thus ...
about 5 years ago in Jedox Platform / Integrator 3 Future Consideration

To enable users to lock data at month and version dimension for fincon model

For example, After performing 2023-12 consolidation, users should be able to lock all data relating to Actual version and any data 2023-12 and before such that nothing gets changed. current issue: Numbers get changed easily as there is no data loc...
about 1 year ago in Jedox Platform / In-Memory DB 0 Future Consideration

Create a connector for the DuckDB database

Offering a native DuckDB connector first would give Jedox a commercial advantage with data-driven teams and pave the way for scalability via MotherDuck without changing the API.
5 months ago in Jedox Platform / Integrator 0 Future Consideration

Enable SSO usage in JedoxOLAP connections (Integrator) across different OLAP instances

Currently the option SAML / SSO authentication and session handling are not designed or implemented to be shared across different OLAP instances. It would be great the be able to trigger a user authentication across different OLAP instances via Je...
5 months ago in Jedox Platform / Integrator 0 Future Consideration

New log level "Info+"

it could be usefull to have a new log level "Info+" : sometimes it is useful to log informations that are relevant and that you want to catch attention to, but you do not want to cause a warning. A new method "LOG.infoPlus()" or something would be...
about 5 years ago in Jedox Platform / Integrator 1 Future Consideration

Two Factor Authentication for Jedox Native Users

Allow Native Jedox user accounts to be setup with two factor authentication.
almost 4 years ago in Jedox Platform / In-Memory DB 0 Future Consideration