![]() |
VOOZH | about |
Google Data Fusion allows users to perform self-service data integration to consolidate disparate data. Uploading the CData JDBC Driver for Paylocity enables users to access live Paylocity data from within their Google Data Fusion pipelines. While the CData JDBC Driver enables piping Paylocity data to any data source natively supported in Google Data Fusion, this article explains how to pipe data from Paylocity to Google BigQuery,
Upload the CData JDBC Driver for Paylocity to your Google Data Fusion instance to work with live Paylocity data. Due to the naming restrictions for JDBC drivers in Google Data Fusion, create a copy or rename the JAR file to match the following format driver-version.jar. For example: cdatapaylocity-2020.jar
With the JDBC Driver uploaded, you are ready to work with live Paylocity data in Google Data Fusion Pipelines.
NOTE: To use the JDBC Driver in Google Data Fusion, you will need a license (full or trial) and a Runtime Key (RTK). For more information on obtaining this license (or a trial), contact our sales team.
Set the following to establish a connection to Paylocity:
This property is required for executing Insert and Update statements, and it is not required if the feature is disabled.
Paylocity will decrypt the AES key using RSA decryption.
It is an optional property if the IV value not provided, The driver will generate a key internally.
You must use OAuth to authenticate with Paylocity. OAuth requires the authenticating user to interact with Paylocity using the browser. For more information, refer to the OAuth section in the Help documentation.
The Pay Entry API is completely separate from the rest of the Paylocity API. It uses a separate Client ID and Secret, and must be explicitly requested from Paylocity for access to be granted for an account. The Pay Entry API allows you to automatically submit payroll information for individual employees, and little else. Due to the extremely limited nature of what is offered by the Pay Entry API, we have elected not to give it a separate schema, but it may be enabled via the UsePayEntryAPI connection property.
Please be aware that when setting UsePayEntryAPI to true, you may only use the CreatePayEntryImportBatch & MergePayEntryImportBatchgtable stored procedures, the InputTimeEntry table, and the OAuth stored procedures. Attempts to use other features of the product will result in an error. You must also store your OAuthAccessToken separately, which often means setting a different OAuthSettingsLocation when using this connection property.
For assistance in constructing the JDBC URL, use the connection string designer built into the Paylocity JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.paylocity.jar
Fill in the connection properties and copy the connection string to the clipboard.
π Using the built-in connection string designer to generate a JDBC URL (Salesforce is shown.)With the Source and Sink configured, you are ready to pipe Paylocity data into Google BigQuery. Save and deploy the pipeline. When you run the pipeline, Google Data Fusion will request live data from Paylocity and import it into Google BigQuery.
π Image
While this is a simple pipeline, you can create more complex Paylocity pipelines with transforms, analytics, conditions, and more. Download a free, 30-day trial of the CData JDBC Driver for Paylocity and start working with your live Paylocity data in Google Data Fusion today.
Download a free trial of the Paylocity Driver to get started:
Download NowLearn more:
π Paylocity IconRapidly create and deploy powerful Java applications that integrate with Paylocity.