Ideas

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.

Allowing Actions on Labels were initially disallowed because strictly speaking Labels should just be a visual object. However, labels have a lot more formatting capabilities than buttons, combo boxes or lists. For example, vertical centering, word...

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...

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 ...

For the moment, we can't have a scheduler action and then a download file action. (The download action is lauched before the end of the scheduler). It will be interresting to have the option "Wait for job to be done" (like with integrator action) ...

It is a simple thing but the way the dimensions are ordered on the left side do not follow any useful criteria. It would be nice to have something similar to what we have in subset editor where you can type the name or part of it in a field and it...

The "Session Data Missing" warning indicates that the session cookie was not found. I don't think that it still serves a purpose and it is shown for almost every user.

In many reports I need to consider date intervals. for example beginning is 2012-11 and end is 2015-03 Calendar is - All Years - Year - Quar. - Month So a macro calculates all needed Elements: - 2011-11, 2011-12, 2012, 2013, 2014, 2015-Q1 This is...

Navigating from a scheduled task in task scheduler to the actual ETL component (groovy/ standard job, etc) would be handy. Right clicking and selecting an option to navigate to the respective ETL component would save a lot of time in implementatio...

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...