This page describes how to use CData Sync to extract data. The load-from-file extraction method that is used as an example, which is available in all UiPath Process Mining Connectors.
The default extraction tool for connectors is CData Sync. With CData Sync you can define connections to extract data from a source to a destination. See the illustration below for an overview.
For general instructions on how to use CData, see the official CData Sync documentation Getting Started with CData Sync.
CData Sync is only used for extracting data and not for applying data transformations. Therefore, the transformation functionality in CData Sync is not used.
The default extractor that should be available in any connector is the load-from-file extractor.
The load-from-file extraction method is available in all connectors. This extraction method loads data from
.csv files and stores it in a SQL Server database with the use of CData Sync.
Follow these steps to create the source connection.
Click on Connections and select type CSV on the Sources tab of the Add Connection dialog.
Set the URI to the path where the
Select the Connection String option button.
Enter the connection string in the Connection String field:
Siehe Abbildung unten.
Follow these steps to create the destination connection.
Go to the Destinations tab in the Add Connection dialog and define a new connection of type SQL Server.
Configure the settings to connect to your SQL Server database.
Siehe Abbildung unten.
Follow these steps to create the job.
Add a new job.
Set the source connection to the
Set the destination connection to the SQL Server connection.
Go to the Advanced tab, and set your database schema as the
Enable the checkboxes
Go to the Tables tab and click on Add custom query. Enter a query of the following form to select the files of the source:
Click on Save Changes.
The column mappings in the job settings, will be set automatically and do not have to be changed.
If you want to use DataBridgeAgent for loading data into a MS SQL Server database, the custom query has to mirror the output of the connector you are using. For example, for the SAP connector for Purchase-to-Pay discovery accelerator, the query would look like this:
REPLICATE [Accounting_documents_base_raw]; REPLICATE [Events_base_raw]; REPLICATE [Goods_receipt_base_raw]; REPLICATE [Invoice_items_base_raw]; REPLICATE [Invoices_base_raw]; REPLICATE [Payments_base_raw]; REPLICATE [Purchase_order_items_base_raw]; REPLICATE [Purchase_orders_base_raw]; REPLICATE [Purchase_requisitions_base_raw];
To run the extractor, execute the script
cdata-extraction.ps1 that can be found in the scripts folder of the connector repository. For more information on running the extractor script, see Running a SQL connector.
Aktualisiert vor 3 Monaten