![]() |
VOOZH | about |
CData Sync is a standalone application that supports a wide range of replication scenarios, including replicating both sandbox and production instances into your database. By replicating Paylocity data to a PostgreSQL database in Heroku, you can access Paylocity external objects (via Salesforce Connect) alongside standard Salesforce objects.
For this replication example, you need the following:
Using CData Sync, you can easily replicate data from Paylocity data to a PostgreSQL database on Heroku. For this article, you will need an existing PostgreSQL database on Heroku. To add your PostgreSQL database as a replication destination, navigate to the Connections tab.
You are now connected to PostgreSQL and can use it as both a source and a destination.
NOTE: You can use the Label feature to add a label for a source or a destination.
π Add a label.You can configure a connection to Paylocity from the Connections tab. To add a connection to your Paylocity account, navigate to the Connections tab.
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 Source connection (Salesforce is shown).
CData Sync enables you to control replication with a point-and-click interface and with SQL queries. For each replication you wish to configure, navigate to the Jobs tab and click Add Job. Select the Source and Destination for your replication.
π Select Source and Destination connections for the replication.To replicate an entire table, navigate to the Task tab in the Job, click Add Tasks, choose the table(s) from the list of Paylocity tables you wish to replicate into PostgreSQL, and click Add Tasks again.
π Choose entire tables to replicate (Salesforce is shown).You can use the Columns and Query tabs of a task to customize your replication. The Columns tab allows you to specify which columns to replicate, rename the columns at the destination, and even perform operations on the source data before replicating. The Query tab allows you to add filters, grouping, and sorting to the replication with the help of SQL queries.
π Configure a replication.As you make changes using the interface, the SQL query used for the replication changes, going from something simple, like this:
REPLICATE [Employee]
to something customized and more complex, like this:
REPLICATE [Employee] SELECT [FirstName], [LastName] FROM [Employee] WHERE [EmployeeId] = 1234
Select the Overview tab in the Job, and click Configure under Schedule. You can schedule a job to run automatically by configuring it to run at specified intervals, ranging from once every 10 minutes to once every month.
π Schedule your job to run automatically.Once you have configured the replication job, click Save Changes. You can configure any number of jobs to manage the replication of your Paylocity data to PostgreSQL.
Once all the required configurations are made for the job, select the Paylocity table you wish to replicate and click Run. After the replication completes successfully, a notification appears, showing the time taken to run the job and the number of rows replicated.
π Run the job.The Paylocity data tables are now replicated in Heroku PostgreSQL database.
Once your Paylocity data is replicated to the PostgreSQL database on Heroku, configure the OData interface for Heroku and connect to the database as an external data source via Salesforce Connect.
The first part of connecting to Paylocity data replicated to a PostgreSQL database on Heroku is configuring the Heroku External Objects for the database.
Refer to the Heroku documentation for more detailed instructions.
After the OData service for Heroku is configured, we can connect to the replicated Paylocity data as an external data source from Salesforce Connect.
After you have created the external data source in Salesforce, follow the steps below to create Paylocity external objects that reflect any changes in the data source. You will synchronize the definitions for the Paylocity external objects with the definitions for Paylocity tables.
At this point, you will be able to connect to and work with your replicated Paylocity entities as external objects just as you would with standard Salesforce objects, whether you are simply viewing the data or building related lists of external Paylocity data alongside standard Salesforce objects.
Download a 30-day free trial of CData Sync and replicate your Paylocity data for use with Salesforce Connect today!
Learn more or sign up for a free trial:
CData Sync