Ideas

Reports created with legacy add-in should be usable without the need to detach views & rebuild them in new add-in. This will help users collaborate easily using 2 different add-ins depending on their setup.

By adding Jedox Logs to the OData Hub, users could access the logs from tools like PowerBI instead of the only the console. This would also allow to integrate logs in automation.

At the moment I need to adapt all formulas I create in Jedox manually when I want to switch between the connection to our dev and live instance. It would help if the Excel Add-In would directly enable a variable as an input for a connection e.g. i...

PALO.DATA.SOURCE Identify rule-based values/cells Function to identify, if a value is calculated or stored in the database. This enables dynamic reports where a conditional formatting opens cells for data entry ONLY if they are actually stored an...

Be able to restrict access to ODATA to certain users/groups independently of access to other Jedox objects.

It would be really helpful if the new add-in could allow functionality to run scheduler jobs direct from the excel add-in. Even better if the job could be applied to a button-click within excel

An example cube with rules (currency conversion, version blending, hr headcount rule, etc) would be great.

The "Drill By..." is an excellent addition to Jedox Web. Can the capability be extended to the Excel Add-in please.

In the enterprise environment, the Basic Auth in the ODATA Hub is not sufficient and it becomes necessary to use stronger authentication methods. A best practice here would be the additional authentication with a client certificate.

In Views, rows can be filtered by an attribute value (or Alias). However, if the user picked a Alias format (such as "Element name (Alias"), this can lead to result which might be unexpected. For example, when filtering for "start with" + some cha...