![]() |
VOOZH | about |
QuerySurge is a smart data testing solution that automates data validation and testing. When paired with the CData JDBC Driver for Paylocity, QuerySurge can work with live Paylocity data. This article explains how to connect to Paylocity data from QuerySurge.
With built-in optimized data processing, the CData JDBC Driver offers unmatched performance for interacting with live Paylocity data. When you issue complex SQL queries to Paylocity, the driver pushes supported SQL operations, like filters and aggregations, directly to Paylocity and utilizes the embedded SQL engine to process unsupported operations client-side (often SQL functions and JOIN operations). Its built-in dynamic metadata querying allows you to work with and analyze Paylocity data using native data types.
To connect to live Paylocity data from QuerySurge, you need to deploy the JDBC Driver JAR file to your QuerySurge Agent(s) and add a new connection from the QuerySurge Admin view.
For more information on deploying JDBC drivers for QuerySurge, refer to the QuerySurge Knowledge Base.
Set the Connection URL using the necessary connection properties to authenticate with Paylocity. Your Connection URL will look something like the following:
jdbc:paylocity:OAuthClientID=YourClientId;OAuthClientSecret=YourClientSecret;RSAPublicKey=YourRSAPubKey;Key=YourKey;IV=YourIV;InitiateOAuth=GETANDREFRESH;
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.
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.
π Using the built-in connection string designer to generate a JDBC URL (Salesforce is shown.)
Once the connection is added, you can write SQL queries against your Paylocity data in QuerySurge.
With the connection configured, you can follow the steps below to compare querying Paylocity data with a QueryPair.
Download a free, 30-day trial of the CData JDBC Driver for Paylocity and start working with your live Paylocity data in QuerySurge. Reach out to our Support Team if you have any questions.
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.