It is not possible to writeback a null directly from the lookup function.
This would be usefull for possible writebacks to a SQL database. As this would require less space within the SQL database.
The workaround for now is using a extra groovy function in order to get the etl to write back a null.1 vote
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 :)19 votes
I think it would be utterly helpful to add an instruction like "show warnings without import". This would make it possible to update basic data (i. e. Dimensions) before importing.
One can of course delete the imported data and reimport, but if you use "Cube Load with Drillthrough", then you will end up with plenty of double entries here, since this is a separate database...1 vote
Having huge integrator projects makes it confusing to find a component that failed in etl process for example. The components (Extracts, Transforms, Jobs, ...) are part of the logfiles shown in the monitor but in case of failure of in case of the need to get some details it is necessary to go to the concrete extract, transform, job and so on.
The feature request is now to show the displayed components in the monitor log file as link that points to the component inside the integrator. So only one click is needed to jump to the concerned component.5 votes
It would be very useful to have the possibility defining global Variables, Connections etc... (Perhaps even extracts!)
In Case e.g. an IP-Adress of a source-server changed it is not longer necessary to change all the concerned connections in the projects, but only the one global defined connection...3 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.24 votes
Jedox is using a customized Groovy implementation.
This does not contain all functionality of groovy!!!!!!
does not state a hint that not all native groovy functions are supported.
e.g AntBuilder() is missing in Jedox 7.
Either change the doku, give a list of all supported functions or provide the full function catalogue of groovy by adding the missing libraries.
Also the groovy version used would be nice to now.25 votes
if a job using this variable connection is still running => message to the user / allow to cancel the job9 votes
this would be greatly useful to have a method to get the number of rows returned by an ETL component, such as:
At the present time only GET and POST are supported. It would be great to have all the other methods of REST (PUT, DELETE...)9 votes
In the US we are seeing increasing demand for integrating Workday HR data into planning processes based on other sources (NetSuite, SAP, and other ERP systems, Qlik on the frontend). Workday They already has a relationship with Adaptive Insights and offer their own solution for Planning, Budgeting, and Forecasting. We would be competing against them in deals that lead with planning for Workday as a requirement but in other deals having a Workday integration solution may help us against Adaptive, especially if the project goals include other areas where Jedox is strong (flexibility, Qlik integration, etc.).6 votes
According with the customer support channel, this connection is not possible due to:
Microsoft uses rest api to connect its modules, like share-point and other products. These modules are authenticated with auth2 type(also handled via rest calls). Your example uses basic authentication which is not a correct way to connect share-point. So, as a result, this is normal to have this error.
This connection would be very usefull3 votes
Several prospects we met recently are using Netsuite. A dedicated connector would be nice.3 votes
Would be nice to have a dedicated Quickbooks connector. Many smaller prospects we have met recently at trade shows are still using Quickbooks.4 votes
In addition to the "Export Data" function which generates a CSV files that opens in Excel, we would like to see a function for just copying data to the clipboard for manual paste into an already open Excel sheet. This will make data analysis/reconciliation easier, when you can just paste it into the next sheet, instead of opening a new Excel workbook.6 votes
Current SOAP/Webservice connector in Jedox Integrator does not support webservices that have Basic Authentication in front of the service.
Microsoft Dynamics Webservices requires authentication in front of the Webservice due to the sensitive nature of the content.
This means that we can not e.g. connect to a cloud based Dynamics instance, via its webservices directly from Integrator.
Dynamics supports both SOAP and OData protocols.11 votes
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).11 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 JC13 votes
Sometimes a variable in ETL is just a simple math calculation based on another variable.
Example: year_end = year_start + 10
Another case would be a simple "if then else" condition based on another variable.
It would be great to just define such formulas directly in the variables section of the ETL project.
Right now you would need a separate groovy job for this which is too much overhead for this simple task
and creates unnecessary complexity within the flowchart / ETL process.8 votes
- Don't see your idea?