Error in field transform would return the function name where the error occurs.
When a function in field transform runs into an error, its now pretty hard to investigate which function resulted in an error. Intsted of this, the error message should tell more about which function has an error, or, in the field transform data p...
In integrator, it would be very useful if we could generate a global field transform (within a project, or within a certain workspace). For example, during data inputs, customer ID should be processed by a groovy, concatenation, or any other field...
Include "Column Exclude pattern" into Table View Transformation
Many times, a Table View Transformation is the final step of loading data into different sources. It would therefore be very handy to also have the Column Exclude/Include patterns in this transformation. This way, you don't have to define the whol...
When there's an error in one of the columns due to a wrong format or null values in some cells, the Excel Extract will not load and instead return an error. An option to either ignore the format of columns or ignore columns entirely, if they're no...
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 ...
Increase the size of some ETL- input fields for better handling and input
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.
Customizable Naming Conventions for Integrator Projects
Currently, when creating a new Extract within the Integrator, the system automatically generates a default name, such as "New Excel Extract." However, given the varying preferences of consultants, it would be beneficial to offer users the option t...
Search for "name"/"description" within Jedox Integrator
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 ...
When creating a json extract the different column names can be defined. This would be great that it does not have to be defined manually but dynamically, I see 2 possibilities: 1/ getting the column list from another extract or transform 2/ have a...
It would be much easier to work with the monitor if its possible to right click on a warning message and have the option to jump directly into the function (fieldtransform, extract or whatever) where the warning message comes from.
