Ideas

Currently only one azure group can be handed over to Jedox while using the in authorization mode. As our users are working in different models and should have different right settings there, we need multiple groups. This is not possible at the mom...

As we were running our yearly planning this year, we had the problem that in the early afternoon the memory limit of the SSS was reached and the service crashes / restartet. After a lot of mails with the support team, I got the answer that it is n...

Have a flag per dimension indicating which alias to use when drilling-by so users don't need to adjust the dynatable each time. Example: Element "12345" from Customer dimension is not understandable. If instead, the name (flag of default attribute...

The functionality to constraint attribute values via a Domain (currently available in the Modeler) should be also available a) when uploading a dimension from a file with the Modeler, b) when loading a dimension with Integrator, c) when enteri...

Currently, Jedox users have to specify a SMTP server, user, and password they own to send mails from Jedox (e.g. Batch PDF, Integrator task status mails etc.) Request is that Jedox instead offers / uses a SMTP gateway / SMTP relay server. User wou...

It's great that we now get better customizing of charts via the "Advanced Chart Properties". But it is still limited when it comes to more interactive charting and reporting. I would like to insert @Variables into the JSON string so more propertie...

When a Jedox instance has a connection to another database and cube (through Administration->Connections) it is possible to access and view this data through a view query in the report designer. However one cannot build a dynatable with this da...

When adding a label to the canvas, it seems to format everything as a general format with ability to format the font and font size. I had a few occasions where I needed to use an expression and format the result in the label (e.g. expression - =TO...

There's often a significant number of databases present in a Jedox environment, with possible several people working on them and several usecases. To allow keeping track of what specific databases are used for, who works on them etc., it would be ...

Basically expose in the macro engine all what is possible to do in a spreadsheet: - create / rename / delete / hide / show sheet - insert / delete columns/rows - you name it