E-mails sent by ETL-/Taskmanager shall be more configurable:
- User defined mail subject incl. use of ETL variables
- User defined mail body incl. use of ETL variables, incl. HTML
- Mail recipients: TO/CC/BCC
- Possibility to attach statical files in addition to the batch-PDF.
- Configurable layout templates50 votes
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
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 used in parallel within one job should be configurable.16 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)
Actually the groovy function editor is not reflecting the high maturity which Jedox Integrator has reached now.
You cannot even resize it if you have to develop a more extended logic.
More real-time validation of the code and debugging support would also bring a big value add.15 votes
At the moment drill through works only with one database.
Filling a cube from different sources with the need of different drill through information is not possible.
It would be nice to use different databases as source for drill through.15 votes
There is no way of undoing a change in ETL 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 ETL component without saving it.13 votes
instead of forcing the creation of folders by component type (e.g. "Cube", "Dimension", .. for extracts), it would be very much appreciated, if it was possible to create a folder-structure by user.
Potentially, these folders could also span across "E", "T" and "L", to allow even easier structuring by topics.
Not sure though, if the latter brings more advantages or disandvantages. Please post your comment.13 votes
When loading data into relational database, the Jedox ETL commit the data every 1000 records by default, and it's not possible to change the commit size to "unlimited".
Therefore, if the data loading was failed at the middle of the execution, the halfway data may remain in the target database after the execution.
To avoid the problem, the Jedox ETL need to have the rollback functionality.10 votes
Navigating from a scheduled task in task scheduler to the actual ETL component (groovy/ standard job, etc) would be handy. Right clicking and selecting an option to navigate to the respective ETL component would save a lot of time in implementations with a large number of scheduled jobs across many projects.9 votes
It would be great to be able to change default values of variables
without leaving the current component.
..e.g. via a sidebar or popup.
This would make development and testing more efficient.
Currently whenever you need to change a variable value while you are editing an extract, transform or load you need to jump into the variables tree, which implicitelly closed the current view.9 votes
oad multiple Excel files from a directory with one connection and extract (like CSV Files).
Basicly the same structure like creating a file extract using a folder-connection. But also working with Excel files :)8 votes
this would be greatly useful to have a method to get the number of rows returned by an ETL component, such as:
In the integrator > field transform, i would like to use the same function for several different transforms. More specifically, i'm using a map and I'd like to use the same map in other transforms without retyping it (or updating it individually).8 votes
When creating ETL project, a lot of debugging is needed. At this moment to check if data is correct, I'm exporting data to CSV right from DataPreview vindow. The problem - it exports only data visible on screen.
Sure - with BIG data, it is ok.
Add search and filter functionality to DataPreview window. Any column would be searchable and filtrable. Something like Data Filter in Excel.
It would exclude any exporting for debugging purposes.8 votes
User-defined nodes should be allowed in the integrator.
Currently, there are "Global Projects" and "Models". If a new node can be created for models, this should technically be no problem for other user-defined nodes.
These can be used to structure more complex projects – and it would allow partners/consultants to separate different customer projects (for this, additional sub-projects and/or folders would also be helpful).
But as a start it would be a huge benefit to use the current structure and just add a user dialogue to add/delete projects nodes on the same level as "global" or "models".7 votes
So that administration of the scheduler jobs is possible.
For example to manage active and inactive jobs.
(Enable or disable jobs all at once)6 votes
It would be great to filter and rename the set of output columns directly within table joins, table views and extracts
...similar to field transforms. (see screenshot)
This would save time as well as a couple of additional elements in the ETL flow chart.
Today after table joins I often add an additional field transform because I only need maybe 3 out of 10 columns from the join...and maybe 2 of them with another name.
Thanks JC6 votes
This would be great to be able to deactivate filters in Extracts. For instance, Extract cube, I have 3 rows, and I want to remove the 2nd temporarily. At the present time I have to delete it, I would like to be able to deactivate it only.5 votes
We have split our ETL processes into several different Integrator projects to keep everything modular and maintainable.
However the deployment of a new complete release from a development to a production system is quite annoying:
We have to export every single project separately.
And on the production sides it is the same:
We have to import every single project separately.
It would be great to be able to do this in one step.
Thanks :)5 votes
- Don't see your idea?