![]() |
VOOZH | about |
Google Cloud Data Fusion simplifies building and managing data pipelines by offering a visual interface to connect, transform, and move data across various sources and destinations, streamlining data integration processes. When combined with CData Connect AI, it provides access to Paylocity data for building and managing ELT/ETL data pipelines. This article explains how to use CData Connect AI to create a live connection to Paylocity and how to connect and access live Paylocity data from the Cloud Data Fusion platform.
Connectivity to Paylocity from Cloud Data Fusion is made possible through CData Connect AI. To work with Paylocity data from Cloud Data Fusion, we start by creating and configuring a Paylocity connection.
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.
π Configuring a connection (Salesforce is shown)
When connecting to Connect AI through the REST API, the OData API, or the Virtual SQL Server, a Personal Access Token (PAT) is used to authenticate the connection to Connect AI. It is best practice to create a separate PAT for each service to maintain granularity of access.
With the connection configured and a PAT generated, you are ready to connect to Paylocity data from Cloud Data Fusion.
Follow these steps to establish a connection from Cloud Data Fusion to Paylocity through the CData Connect AI JDBC driver:
jdbc:connect:AuthScheme=Basic;user=username;password=PAT;
Please be aware that there is a known issue in Cloud Data Fusion where "int" types from source data are automatically cast as "long".
Now you have a direct connection to live Paylocity data from from Google Cloud Data Fusion. You can create more connections to ensure a smooth movement of data across various sources and destinations, thereby streamlining data integration processes - all without replicating Paylocity data.
To get real-time data access to hundreds of SaaS, Big Data, and NoSQL sources (including Paylocity) directly from your cloud applications, explore the CData Connect AI.
Learn more about CData Connect AI or sign up for free trial access:
Free Trial