Ideas

The customer would like to use Token-Based Authentication for JDBC connection (NetSuite in this case) in addition to the User name and Password currently supported. As per Knowledge Base article https://knowledgebase.jedox.com/integration/connecti...

Scenario: User has created dimensions and cubes using Jedox DDM though add-in in month 1. In the next month there are few more new dimension elements and additional cube data which needs to be added to the database.Challenge: the user is comfortab...

Define within the subset, if a drilldown is possible on a consolidated element within a picklist.

Combine the abilities of the REST interface (token authentication) with the file connector (handling of CSV data) -- we actually have a REST inerface which returns CSV data for a GET request and currently, there is no way to import this in Jedox.

It would be useful to allow a quick swap of To and From instead of manually recreating them.

For Excel export (as is already the case with PDF export) it should be possible to export multiple frames at the same time. It should behave in the same way as PDF export with frames. So "use for export" should have the same effect on the Excel e...

As a customer, I would like to be able to access the SVS Editor via Administration (<CTRL>+<M>) and not under Modeler (<CTRL>+<P>). Reasons: 1. Security: ste_olap is the only way to restrict access to the SVS editor. Secur...

For spot data checks, I find it long to switch from modeler to designer, create a spreadsheet, edit the spreadsheet, create a view. I would expect a direct view from Modeler.

We have lots of groups and folders and maintenance is heavy. Each time a new group is created, we have to review almost all secured folders. My suggestion would be to manage this through cube rules.

Create a new load type that allows writing to log files custom messages. Currently possible with LOG.info and a groovy script job. It would be better if groovy jobs were not required.