Ideas

In 25.1, using Variables as argument (path parameter) is limited to object RunLoadWithVariables or RunLoadWithVariables. It would be interesting to generalize this to other objects such as GetExtractRows and GetTransformRows. OData Hub is used to ...

On mobile app, the native canvas export button and "export to Excel" is not available, with a message that these actions aren't supported. The request is for the mobile app to support more of these features, just like how they're already available...

I have generated a link to a web report in the standalone mode and unchecked everything in the interface section. However, when I click the link on my mobile and it opens up in the mobile app it shows the report title on top. Can you please add a ...

In the olap Plan & Forecast App there was a functionality that you could double-tap and then swipe on the starting screen with two fingers and then the logs of the mobile app were displayed. There were additional two buttons to be able to send...

With the new Jedox mobile app (old app had a zoom function), you aren't able to zoom in or out on a large report designed from the Web. So as a workaround you have to create separate "mobile" reports (so one report for Jedox Web and a separate one...

With Jedox mobile, you can zoom in on a large report designed from the Web but you can't zoom out to see the entire report.

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.

Possibility of centralized deactivation of smooth scolling mode in the mobile app for all users of a cloud instance

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

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.