![]() |
VOOZH | about |
This article illustrates using the Harvest ADO.NET Data Provider within a SQL Server SSIS workflow for the direct transfer of Harvest data to a Microsoft SQL Server database. It's worth noting that the identical process detailed below is applicable to any CData ADO.NET Data Providers, enabling the direct connection of SQL Server with remote data through SSIS.
In the Data Flow screen, add an ADO.NET Source and an OLE DB Destination from the toolbox.
👁 The components used in the data task in this example.In the connection manager, enter the connection details for Harvest data.
Start by setting the Profile connection property to the location of the Harvest Profile on disk (e.g. C:\profiles\Harvest.apip). Next, set the ProfileSettings connection property to the connection string for Harvest (see below).
To authenticate to Harvest, you can use either Token authentication or the OAuth standard. Use Basic authentication to connect to your own data. Use OAuth to allow other users to connect to their data.
Using Token Authentication
To use Token Authentication, set the APIKey to your Harvest Personal Access Token in the ProfileSettings connection property. In addition to APIKey, set your AccountId in ProfileSettings to connect.
Using OAuth Authentication
First, register an OAuth2 application with Harvest. The application can be created from the "Developers" section of Harvest ID.
After setting the following connection properties, you are ready to connect:
Open the DataReader editor and set the following information:
SELECT Id, ClientName FROM Invoices WHERE State = 'open'
Open the OLE DB Destination and enter the following information in the Destination Component Editor.
Configure any properties you wish on the Mappings screen.
👁 Input and destination columns in the OLE DB Destination Editor.Connect to live data from Harvest with the API Driver
Connect to Harvest