Ideas

Like in write back (dyna) tables in web spreadsheets it is necessary to define allowed entry values. This means e.g. from a dimension subset or a manual/dynamically defined list. Instead of formulas an expression would make sense.

When executing an Integrator job that writes data to a database with limited user permissions in that database, it could happen that the job does not complete successfully because some write actions fail (due to missing permissions of the user). I...

Create either a Groovy script or a custom-built connector to load MT940 SWIFT data to Jedox. The process would include parsing the MT940 files to extract transactional details (e.g., account balances, debits, credits, and statements) and transform...

Choose several ETL components of one project which belong somehow logically together and group them under a given name. Should be displayed in ETL Manager under a new item -Tags --- SalesRelated ------Extract --------- E_XY_1 --------- E_XY_2 ----...

As I have been informed by Jedox Dev team, the ETL-Server (Tomcat Service) is running one job per CPU core. This behaviour is mainly slowing down our ETL projects since a huge amount of data has to be proceeded. The number of cores that should be ...

Actually, we could only change logo, bakground color, add message text, add banner. It would be better if we could customize the login page adding our own link, or remove existing link. Published a link standalone instead of studio by default The ...

When adapting or extending a Jedox environment you often need to create new users/user groups/roles that are only slightly different from the ones that are already existing. Right now you need to create those users/roles/user groups from sratch an...

There is no way of undoing a change in Integrator rather than reloading the whole ETL Project. Once a change has been made one is forced to save! Would be helpful if you can leave a changed integrator component without saving it.

It's necessary to add Planning Assistant to Datatable the same way as in the reports, because users don't know all the splashing commands.

Basic reporting functionalities like scaling factors, number format should be available at report level as a standard like zero suppression Users should be able to decide scaling factors on the fly if they wish to see numbers in absolute value or ...