Using Chain to Extract Data from a Database or ERP then load the Data into a WData Table/Query
Hi,
I am looking for options to use a chain to extract the data from a DB or an ERP, load it into a WData Table then use Query for further processing. I read through support docs, community posts, and other sources, but there isn't a direct connection. if I am using a chain to pull data, I can only put them into a spreadsheet and the table only accepts manual CSV file uploads. Is there a way within the chain to extract data and load the table directly? If this direct passage isn't available, what's the best alternative, I'd like it to be as one button push as possible.
Thanks.
-
Hi Jase. Chains would be a great solution for this. The first step is to review the list of Connectors to identify the one that would be best for your database or ERP system. A list of them can be found here https://support.workiva.com/hc/en-us/articles/360035643892-Connector-types. I also recommend reviewing the various Chain templates and samples as these can make Chain building quicker, easier, and simpler. Specifically, the Load Data to Wdata template is helpful for adding logic into your Chain to load data into a Wdata Table. Combining these together could allow you to build a Chain to extract data from a database or ERP and then load it into a Wdata Table.
0Hi Jeff,
Thanks for the suggestion. I do have follow-up questions:
If I use a MySQL connector to extract a dataset, the connector generates the output in a CSV file, how does it feed into a data file that's a required item for the load data chains?
Do I use the "Create Files" connector in the File Utilities bucket or the "Workiva" bucket? And where would this created file be saved?
Thanks.
0Hi Jase. If you are using either Execute Query or Execute SQL MySQL Commands, both will output a "Result Set" on success. This is a CSV file that can be passed into the Data File runtime input of the Load Data to Wdata template. You would not need to use a Create Files Command to generate the CSV file.
0Please sign in to leave a comment.
Comments
3 comments