![]() |
VOOZH | about |
This article illustrates using the Procore ADO.NET Data Provider within a SQL Server SSIS workflow for the direct transfer of Procore 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 Procore data.
Start by setting the Profile connection property to the location of the Procore Profile on disk (e.g. C:\profiles\Procore.apip). Next, set the ProfileSettings connection property to the connection string for Procore (see below).
To authenticate to Procore, and connect to your own data or to allow other users to connect to their data, you can use the OAuth standard.
First, register an OAuth application with Procore. You can do so by logging to your Developer Account and going to Create New App. Follow all necessary steps to register your app. First create a new version of Sandbox Manifest and then promote it to Production in order to get your Production Crendentials. Your Oauth application will be assigned a client id and a client secret.
After setting the following connection properties, you are ready to connect:
Open the DataReader editor and set the following information:
SELECT Id, Name FROM Companies WHERE IsActive = 'true'
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 Procore with the API Driver
Connect to Procore