when writing macros or script code in ETL it is often difficult to find out what went wrong and when it went wrong.
The only way at the moment is to scan the log files for error messages.
For development it would be helpfull to have a debug mode for those scripts and macros to see step by step if they are working correctly.
This could be combined with the object manager I proposed within another feature request.42 votes
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
A component may be assigned in different tags
Option to create a tag out of the dependency of a component (to decide if dynamic or not)
ETL jobs often get data from user input or automatically retrieve variable values. This is used to temporary 'overwrite' variable defaults. When debugging an ETL process with many variables you need to manually change all used variables in order to reproduce a previously ran ETL job. It would be nice to have a single button to set all used variables from a specific ETL job to the actual used values (as shown in the integrator logs).4 votes
We’ve added this idea to ourt backlog for further review and later implementation.
In Jedox integrator the additional optional settings are not expanded.
Therefore you always have to expand this block first to check if there is anything configured there.
>> All blocks should always be expanded at any time.
>> Alternatively all blocks should be expanded if they contain any settings other than default.3 votes
We’ve added this request to our feature backlog.
- Don't see your idea?