Possibility to restore old versions in the designer / integrator
If you work on a report or an integrator project and save it, you realize that you would like to restore your version from 1 day / 1 hour ago. An automated possibility for that would be great. Otherwise we always need to store our projects / desig...
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 function...
when using the methode FILE.zip(connName,sourceConnName) in the FILE api, it is not possible to zip mutliple files on the root of the zip file (directory works) this would be helpful since specific systems ingest a zip file without subdirectories ...
Scheduler Job when copying from one instance to another
With the "Jedox Instance Synchronization" feature, users can copy information from one instance to another, including the scheduler. https://knowledgebase.jedox.com/jedox/maintenance/synchronization.htm After copying from the test environment to t...
Retrieve information from parent node in JSON extract
When hierarchical data is retrieved from a REST endpoint, it's really cumbersome to get that data into a dimension. Imagine, your JSON data has the following hierarchy: Legal entity > Function Area > Cost Center Naturally you'd configure you...
Expand column aggregation to include more than 2 column inputs
It would be great to be able to add additional columns in the Column Aggregation Transformation Function so the aggregation can be calculated based on the unique dimension elements from another column. Currently, it allows max two columns but woul...
As a Data Integrator, I want to see the previous runtime executions in the monitor after the job/load's name was modified and executed.
Currently, if I run the job/load, change the name, run it and check the previous execution (with the initial n...
It would be helpful if you could choose whether a CSV or Excel file should be created when exporting ETL DATA PREVIEW. As is the case when exporting drill-through data.
this would be greatly useful to have a method to get the number of rows returned by an ETL component, such as:
mySource=API.initSource("myExtract");
mySource.getRowCount();