Integrator

ETL Jobs and Loads should display all the components that they are linked to and can be triggered by. For example, these should include scheduled jobs, and buttons in reports that reference them as actions. It would be great if the list is also al...

It would be very useful to have the possibility to instead of only find, to have a find and replace option. Then users could edit things faster and help them spend less time in the editor. The alternative is to copy the text in some other editor. ...

Currently, a new user can have issues in finding specific ETL components, because he has to work backwards from Jobs to Loads to Transforms and try to find the relevant pieces. An easy solution would be to add a "Search" functionality to the main ...

As a consultant, I would like to upload Integrator Projects from an SFTP Server. Basically, we would like to have the basic functionality of the "Import" option within the Integrator as a function that we can use within an ETL Job. This way we cou...

When executing an Integrator job with limited user permissions in a database, it could happen that the job does not complete successfully due to missing permissions of the user. If in that case some write actions were already executed and others a...

Jedox is using a customized Groovy implementation. This does not contain all functionality of groovy!!!!!! The documentation https://knowledgebase.jedox.com/knowledgebase/job-groovy/ does not state a hint that not all native groovy functions are...

Please increase the size of some ETL- input fields, where many characters can be entered.For instance: logical expression fields; json template in JSON connections, etc.The current size is error-prone and inconvenient.

Idea: To communicate with financial institutes companies use the XBRL standard. It would be great to be XBRL certificated. Background: XBRL is a freely available and global framework for exchanging business information. XBRL allows the expression ...

Offering a native DuckDB connector first would give Jedox a commercial advantage with data-driven teams and pave the way for scalability via MotherDuck without changing the API.

Currently the option SAML / SSO authentication and session handling are not designed or implemented to be shared across different OLAP instances. It would be great the be able to trigger a user authentication across different OLAP instances via Je...