Connect to Paylocity Data in ACL Analytics

ACL Analytics, part of Diligent HighBond, is a powerful data analysis software primarily used for audit, risk management, and compliance. It enables professionals to examine and analyze large volumes of data to identify anomalies, trends, and potential risks or fraudulent activities.

CData Connect Cloud offers a dedicated cloud-to-cloud interface for Paylocity, enabling analytics directly from live Paylocity data within ACL Analytics, all without the need for data replication to a native database. With its inherent optimized data processing capabilities, CData Connect Cloud efficiently channels all supported SQL operations, including filters and JOINs, directly to Paylocity. This leverages server-side processing to swiftly deliver the requested Paylocity data.

Configure Paylocity Connectivity for ACL Analytics

Connectivity to Paylocity from ACL Analytics is made possible through CData Connect Cloud. To work with Paylocity data from ACL Analytics, we start by creating and configuring a Paylocity connection in CData Connect Cloud.

1. Log into Connect Cloud, click Sources, and then click Add Connection

2. Select "Paylocity" from the Add Connection panel

3. Enter the necessary authentication properties to connect to Paylocity. Enter the necessary authentication properties to connect to Paylocity.

   Set the following to establish a connection to Paylocity:

   • RSAPublicKey: Set this to the RSA Key associated with your Paylocity, if the RSA Encryption is enabled in the Paylocity account.

     This property is required for executing Insert and Update statements, and it is not required if the feature is disabled.

   • UseSandbox: Set to true if you are using sandbox account.
   • CustomFieldsCategory: Set this to the Customfields category. This is required when IncludeCustomFields is set to true. The default value for this property is PayrollAndHR.
   • Key: The AES symmetric key(base 64 encoded) encrypted with the Paylocity Public Key. It is the key used to encrypt the content.

     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.

   • IV: The AES IV (base 64 encoded) used when encrypting the content. It is an optional property if the Key value not provided, The driver will generate an IV internally.

   Connect Using OAuth Authentication

   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

   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.

4. Click Create & Test
5. Navigate to the Permissions tab in the Add Paylocity Connection page and update the User-based permissions.

Add a Personal Access Token

When connecting to Connect Cloud 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 Cloud. It is best practice to create a separate PAT for each service to maintain granularity of access.

1. Click on the Gear icon () at the top right of the Connect Cloud app to open the settings page.
2. On the Settings page, go to the Access Tokens section and click Create PAT.
3. Give the PAT a name and click Create.
4. The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.

With the connection configured and a PAT generated, you are ready to connect to Paylocity data from ACL Analytics.

Connect to Paylocity from ACL Analytics

The steps below outline connecting to CData Connect Cloud from ACL Analytics to create a new Paylocity data source. The CData Connect Cloud Virtual SQL Server allows you to establish a connection to your data from integration tools that support connections to SQL servers. The Virtual SQL Server mimics the behavior of a traditional SQL server, and it supports a range of query options.

1. With your Analytics File open, select 'Import' --> 'Database and application'
2. Create a new SQL Server connection
3. Set the connection information
   • Server: tds.cdata.com
   • Port: 14333
   • Auth Scheme: Password
   • Username: a Connect Cloud user, for example, [email protected]
   • Password: the PAT for the above Connect Cloud user
   • Database: the name of your Paylocity connection, for example, Paylocity1
   
4. Click "Test Connection"
5. Click "OK"
6. You are now ready to work with your Paylocity data in ACL Analytics!

Live connections to Paylocity data from your applications

ACL Analytics can now connect to live Paylocity data directly through Connect Cloud, allowing you to analyze Paylocity data without duplicating it.

To get live data access to 100+ SaaS, Big Data, and NoSQL sources directly from your applications, try CData Connect Cloud today!