The CData Sync App provides a straightforward way to continuously pipeline your Paylocity data to any database, data lake, or data warehouse, making it easily available for Analytics, Reporting, AI, and Machine Learning.
The Paylocity connector can be used from the CData Sync application to pull data from Paylocity and move it to any of the supported destinations.
The Sync App leverages the Paylocity API to enable bidirectional access to Paylocity.
For required properties, see the Settings tab.
For connection properties that are not typically required, see the Advanced tab.
Paylocity provides two ways to connect: via the Pay Entry API, and via the standard Paylocity API.
Before you connect, set these properties (if applicable):
For sites that have opted in to encryption:
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.
Notes:
The following subsections describe how to authenticate to Paylocity from the three most common authentication flows.
For a complete list of connection string properties available in Paylocity, see Connection.
Automatic refresh of the OAuth access token:
To have the Sync App automatically refresh the OAuth access token, do the following:
Manual refresh of the OAuth access token:
The only value needed to manually refresh the OAuth access token is the OAuth refresh token.
Store the OAuth refresh token so that you can use it to manually refresh the OAuth access token after it has expired.
This section details a selection of advanced features of the Paylocity Sync App.
The Sync App supports the use of user defined views, virtual tables whose contents are decided by a pre-configured user defined query. These views are useful when you cannot directly control queries being issued to the drivers. For an overview of creating and configuring custom views, see User Defined Views .
Use SSL Configuration to adjust how Sync App handles TLS/SSL certificate negotiations. You can choose from various certificate formats;. For further information, see the SSLServerCert property under "Connection String Options" .
Configure the Sync App for compliance with Firewall and Proxy, including Windows proxies and HTTP proxies. You can also set up tunnel connections.
For further information, see Query Processing.
By default, the Sync App attempts to negotiate TLS with the server. The server certificate is validated against the default system trusted certificate store. You can override how the certificate gets validated using the SSLServerCert connection property.
To specify another certificate, see the SSLServerCert connection property.
The Paylocity Sync App also supports setting client certificates. Set the following to connect using a client certificate.
To authenticate to an HTTP proxy, set the following:
Set the following properties:
This section shows the available API objects and provides more information on executing SQL to Paylocity APIs.
Tables describes the available tables. Tables are statically defined to model resources such as Earnings, LocalTaxes, and EmployeeDetails.
Views describes the available views. Views are statically defined to model resources such as Employees, CompanyCodes, and CustomFields.
Stored Procedures are function-like interfaces to Paylocity. Stored procedures allow you to execute operations to Paylocity, including downloading documents and moving envelopes.
The Sync App models the data in Paylocity as a list of tables in a relational database that can be queried using standard SQL statements.
| Name | Description |
| AdditionalRates | Add/update additional rates |
| Earnings | Get All Earnings. Delete Earning by Earning Code and Start Date. Add/Update Earning. Get Earnings by Earning Code. Get Earning by Earning Code and Start Date |
| EmergencyContacts | Add/update emergency contacts |
| EmployeeBenefitSetup | Add/update employee's benefit setup |
| EmployeeDetails | Add new employee. Get employee. Update employee |
| Input_TimeEntry | To create the csv content for the CreatePayEntryImportBatch.TimeEntry using this as a TEMP Table. When the connection to Paylocity is closed, all tables names started with Input are cleared. |
| LocalTaxes | Get local taxes by tax code. Get all local taxes. Add new local tax. Delete local tax by tax code |
| NonPrimaryStateTax | Add/update non-primary state tax |
| PrimaryStateTax | Add/update primary state tax |
| SensitiveData | Gets employee sensitive data information directly from Web Pay. |
Add/update additional rates
The Sync App will use the Paylocity API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Sync App.
For example, the following queries are processed server side:
SELECT * FROM AdditionalRates WHERE EmployeeId = '123'
Following is an example of how to inserting into AdditionalRates table. For example:
INSERT INTO AdditionalRates (employeeid, Shift, Job, CostCenter1, CostCenter2, CostCenter3, EffectiveDate, ChangeReason, RateCode, Rate, RatePer, RateNotes) VALUES ('123', '1', '0000123', '100', '101', '100', '2021-02-09', 'Cost of Living Increase', 'CN', 500, 'week', 'NewRate')
Following is an example of how to Update a AdditionalRates table:
UPDATE AdditionalRates SET CostCenter1 = '100', ratecode = 'CN', rate = 100, rateper = 'hour' WHERE employeeId = '123'
| Name | Type | ReadOnly | References | Description |
| EmployeeId [KEY] | String | True |
Employees.EmployeeId |
Id of the Employee. |
| CostCenter1 | String | False |
Not required. Valid values must match one of the system coded cost centers available in the Additional Rates Cost Center level 1 drop down. This cell must be in a text format. | |
| CostCenter2 | String | False |
Not required. Valid values must match one of the system coded cost centers available in the Additional Rates Cost Center level 2 drop down. This cell must be in a text format. | |
| CostCenter3 | String | False |
Not required. Valid values must match one of the system coded cost centers available in the Additional Rates Cost Center level 3 drop down. This cell must be in a text format. | |
| RatePer | String | False |
Required. Valid values are HOUR or WEEK. | |
| Rate | Decimal | False |
Required. Enter dollar amount that corresponds to the Per selection. | |
| RateCode | String | False |
Required. If populated, must match one of the system coded values available in the Additional Rates Rate Code drop down. | |
| ChangeReason | String | False |
Not required. If populated, must match one of the system coded values available in the Additional Rates Change Reason drop down. | |
| EffectiveDate | Date | False |
Required. Common formats include *MM-DD-CCYY*, *CCYY-MM-DD*. | |
| EndCheckDate | Date | False |
Not required. Must match one of the system coded check dates available in the Additional Rates End Check Date drop down. Common formats include *MM-DD-CCYY*, *CCYY-MM-DD*. | |
| RateNotes | String | False |
Not required. | |
| Job | String | False |
Not required. If populated, must match one of the system coded values available in the Additional Rates Job drop down. | |
| Shift | String | False |
Not required. If populated, must match one of the system coded values available in the Additional Rates Shift drop down. | |
| CompanyId | String | True |
Id of the Company. |
Get All Earnings. Delete Earning by Earning Code and Start Date. Add/Update Earning. Get Earnings by Earning Code. Get Earning by Earning Code and Start Date
The Sync App will use the Paylocity API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Sync App.
For example, the following queries are processed server side:
SELECT * FROM Earnings WHERE EmployeeId = '123' SELECT * FROM Earnings WHERE EmployeeId = '123' AND EarningCode = '1098' SELECT * FROM Earnings WHERE EmployeeId = '123' AND EarningCode = '1098' AND StartDate = '2019-04-01'
Following is an example of how to inserting into Earnings table. For example:
INSERT INTO Earnings (EmployeeId, EarningCode, StartDate) VALUES ('999621027', '1098', '2020-02-10')
Following is an example of how to update a Earnings table:
UPDATE Earnings SET EarningCode = '1098', StartDate = '2020-02-09' WHERE employeeId = '999621027'
Following is an example of how to delete earnings in the Earnings table:
DELETE FROM Earnings WHERE employeeId = '123' AND EarningCode = '1' AND StartDate = '2021-01-01'
| Name | Type | ReadOnly | References | Description |
| EmployeeId [KEY] | String | True |
Employees.EmployeeId |
Id of the Employee. |
| PaidTowardsGoal | Decimal | False |
Amount already paid to employee toward goal. Decimal(12,2) | |
| MiscellaneousInfo | String | False |
Information to print on the check stub if agency is set up for this earning. | |
| EffectiveDate | Date | False |
Date earning is active. Defaulted to run date or check date based on Company setup. Common formats are MM-DD-CCYY, CCYY-MM-DD. | |
| CostCenter1 | String | False |
Cost Center associated with earning. Must match Company setup. | |
| CostCenter2 | String | False |
Cost Center associated with earning. Must match Company setup. | |
| CostCenter3 | String | False |
Cost Center associated with earning. Must match Company setup. | |
| AnnualMaximum | Decimal | False |
Year to Date dollar amount not to be exceeded for an earning in the calendar year. Used only with company driven maximums. Decimal(12,2) | |
| IsSelfInsured | Bool | False |
Used for ACA. If not entered, defaulted to Company earning setup. | |
| Rate | Decimal | False |
Rate is used in conjunction with the hoursOrUnits field. Decimal(12,2) | |
| Frequency | String | False |
Needed if earning is applied differently from the payroll frequency (one time earning for example). | |
| EndDate | Date | False |
Stop date of an earning. Common formats are MM-DD-CCYY, CCYY-MM-DD. | |
| HoursOrUnits | Decimal | False |
The value is used in conjunction with the Rate field. When entering Group Term Life Insurance (GTL), it should contain the full amount of the group term life insurance policy. Decimal(12,2) | |
| EarningCode | String | False |
Earning code. Must match Company setup. | |
| RateCode | String | False |
Rate Code applies to additional pay rates entered for an employee. Must match Company setup. | |
| Goal | Decimal | False |
Dollar amount. The employee earning will stop when the goal amount is reached. Decimal(12,2) | |
| CalculationCode | String | False |
Defines how earnings are calculated. Common values are *% (percentage of gross), flat (flat dollar amount)*. Defaulted to the Company setup calcCode for earning. | |
| StartDate | Date | False |
Start date of an earning based on payroll calendar. Common formats are MM-DD-CCYY, CCYY-MM-DD. | |
| PayPeriodMaximum | Decimal | False |
Maximum amount of the earning on a single paycheck. Decimal(12,2) | |
| JobCode | String | False |
Job code associated with earnings. Must match Company setup. | |
| Amount | Decimal | False |
Value that matches CalculationCode to add to gross wages. For percentage (%), enter whole number (10 = 10%). Decimal(12,2) | |
| Agency | String | False |
Third-party agency associated with earning. Must match Company setup. | |
| PayPeriodMinimum | Decimal | False |
Minimum amount of the earning on a single paycheck. Decimal(12,2) | |
| CompanyId | String | True |
Id of the Company. |
Add/update emergency contacts
The Sync App will use the Paylocity API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Sync App.
For example, the following queries are processed server side:
SELECT * FROM EmergencyContacts WHERE EmployeeId = '123'
Following is an example of how to inserting into EmergencyContacts table. For example:
INSERT INTO EmergencyContacts (EmployeeId, firstName, lastName, primaryPhone, priority, relationship, MobilePhone, Zip, Notes, Address1, City, County) VALUES ('123', 'firstName', 'lastName', 'M', 'P', 'Brother', 9876543210, 75791, 'Test Notes', 'Address Line1', 'NY', 'USA')
Following is an example of how to Update a EmergencyContacts table:
UPDATE EmergencyContacts SET WorkPhone = '9876543210', firstName = 'firstName', lastName = 'lastName', primaryPhone = 'W', priority = 'S', relationship = 'brother' WHERE employeeId = '999621027'
| Name | Type | ReadOnly | References | Description |
| EmployeeId [KEY] | String | True |
Employees.EmployeeId |
Id of the Employee. |
| FirstName | String | False |
Required. Contact first name. | |
| LastName | String | False |
Required. Contact last name. | |
| MobilePhone | String | False |
Contact Mobile Phone.Valid phone format *(###) #######* or *######-####* or *### ### ####* or *##########* or, if international, starts with *+#*, only spaces and digits allowed. | |
| Zip | String | False |
Postal code. If U.S. address, must be a valid zip code. | |
| Priority | String | False |
Required. Contact priority. Valid values are *P* (Primary) or *S* (Secondary). | |
| Notes | String | False |
Notes. | |
| Address1 | String | False |
1st address line. | |
| Pager | String | False |
Valid phone format *(###) #######* or *######-####* or *### ### ####* or *##########* or, if international, starts with *+#*, only spaces and digits allowed. | |
| WorkPhone | String | False |
Contact Work Phone. Valid phone format *(###) #######* or *######-####* or *### ### ####* or *##########* or, if international, starts with *+#*, only spaces and digits allowed. | |
| PrimaryPhone | String | False |
Required. Contact primary phone type. Must match Company setup. Valid values are H (Home), M (Mobile), P (Pager), W (Work) | |
| Address2 | String | False |
2nd address line. | |
| HomePhone | String | False |
Contact Home Phone. Valid phone format *(###) #######* or *######-####* or *### ### ####* or *##########* or, if international, starts with *+#*, only spaces and digits allowed. | |
| WorkExtension | String | False |
Work Extension. | |
| SyncEmployeeInfo | Bool | False |
Valid values are *true* or *false*. | |
| City | String | False |
City. | |
| Country | String | False |
County. | |
| Relationship | String | False |
Required. Contact relationship. Must match Company setup. Common values are Spouse, Mother, Father. | |
| County | String | False |
Country. Must be a valid 3 character country code. Common values are *USA* (United States), *CAN* (Canada). | |
| String | False |
Contact email. Must be valid email address format. | ||
| State | String | False |
State or Province. If U.S. address, must be valid 2 character state code. Common values are *IL* (Illinois), *CA* (California). | |
| CompanyId | String | True |
Id of the Company. |
Add/update employee's benefit setup
The Sync App will use the Paylocity API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Sync App.
For example, the following queries are processed server side:
SELECT * FROM EmployeeBenefitSetup WHERE EmployeeId = '123'
Following is an example of how to inserting into EmployeeBenefitSetup table. For example:
INSERT INTO EmployeeBenefitSetup (EmployeeId, BenefitSalary, BenefitClass, BenefitSalaryEffectiveDate, BenefitClassEffectiveDate) VALUES ('123', '250', 'FULL', '2021-02-10', '2021-02-10')
Following is an example of how to Update a EmployeeBenefitSetup table:
UPDATE EmployeeBenefitSetup SET BenefitSalary = '250', BenefitClass = 'FULL', BenefitClassEffectiveDate = '2021-02-10', BenefitSalaryEffectiveDate = '2021-02-10' WHERE EmployeeId = '123'
| Name | Type | ReadOnly | References | Description |
| EmployeeId [KEY] | String | True |
Employees.EmployeeId |
Id of the Employee. |
| BenefitSalary | Decimal | False |
Salary used to configure benefits.Decimal(12,2) | |
| BenefitClass | String | False |
Benefit Class code. Values are configured in Web Pay Company > Setup > Benefits > Classes. | |
| BenefitSalaryEffectiveDate | Date | False |
Date when Benefit Salary takes effect. Common formats include *MM-DD-CCYY*, *CCYY-MM-DD*. | |
| DoNotApplyAdministrativePeriod | Bool | False |
Applicable only for HR Enhanced clients and Benefit Classes with ACA Employment Type of Full Time. | |
| IsMeasureAcaEligibility | Bool | False |
Only valid for HR Enhanced clients and Benefit Classes that are ACA Employment Type of Full Time. | |
| BenefitClassEffectiveDate | Date | False |
Date when Benefit Class takes effect. Common formats include *MM-DD-CCYY*, *CCYY-MM-DD*. | |
| CompanyId | String | True |
Id of the Company. |
Add new employee. Get employee. Update employee
The Sync App will use the Paylocity API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Sync App.
For example, the following queries are processed server side:
SELECT * FROM Employee WHERE EmployeeId = '123'
Following is an example of how to inserting into Employee table with aggregate column(Optional). For example:
INSERT INTO AdditionalRates#TEMP (Shift, Job, CostCenter1, CostCenter2, CostCenter3, EffectiveDate, ChangeReason, RateCode, Rate, RatePer, RateNotes) VALUES ( '1', '0000123', '100', '101', '100', '2021-02-09', 'Cost of Living Increase', 'CN', 500, 'week', 'NewRate')
INSERT INTO Employee (FirstName, LastName, MiddleName, Gender, MaritalStatus, PreferredName, PriorLastName, Salutation, Currency, BirthDate, CompanyFEIN, CompanyName, DepartmentPositionChangeReason, DepartmentPositionCostCenter1, DepartmentPositionCostCenter2, DepartmentPositionCostCenter3, DepartmentPositionEffectiveDate, DepartmentPositionEmployeeType, DepartmentPositionIsMinimumWageExempt, DepartmentPositionIsOvertimeExempt, DepartmentPositionIsSupervisorReviewer, DepartmentPositionIsUnionDuesCollected, DepartmentPositionIsUnionInitiationCollected, DepartmentPositionJobTitle, FederalTaxAmount, FederalTaxExemptions, FederalTaxFilingStatus, FederalTaxPercentage, FederalTaxTaxCalculationCode, FederalTaxW4FormYear, HomeAddressAddress1, HomeAddressAddress2, HomeAddressCity, HomeAddressCountry, HomeAddressEmailAddress, HomeAddressMobilePhone, HomeAddressPhone, HomeAddressPostalCode, HomeAddressState, NonPrimaryStateTaxFilingStatus, NonPrimaryStateTaxHigherRate, NonPrimaryStateTaxOtherIncomeAmount, NonPrimaryStateTaxReciprocityCode, NonPrimaryStateTaxtaxCode, PrimaryPayRateAnnualSalary, PrimaryPayRateBaseRate, PrimaryPayRateChangeReason, PrimaryPayRateDefaultHours, PrimaryPayRateEffectiveDate, PrimaryPayRatePayFrequency, PrimaryPayRatePayType, PrimaryStateTaxAmount, PrimaryStateTaxExemptions, PrimaryStateTaxExemptions2, PrimaryStateTaxPercentage, PrimaryStateTaxFilingStatus, PrimaryStateTaxTaxCalculationCode, PrimaryStateTaxTaxCode, PrimaryStateTaxW4FormYear, StatusAdjustedSeniorityDate, StatusChangeReason, StatusEffectiveDate, StatusEmployeeStatus, StatusHireDate, StatusIsEligibleForRehire, TaxSetupSuiState, TaxSetupTaxForm, WorkAddressAddress1, WorkAddressCity, WorkAddressCountry, WorkAddressMobilePhone, WorkAddressPostalCode, WorkAddressState, suffix, IsSmoker, AdditionalRate) VALUES ('TestFirstName1', 'TestLastName', 'TestMiddleName', 'M', 'S', 'Test1', 'TestPrior', 'Mr', 'USD', '1985-11-01', '00-5554442', 'SusanW Z2222 Clone', 'New Hire', '100', '101', '100', '2021-02-01', 'RFT', false, true, false, false, false, 'Clinical Psychologist', '1', '0', 'M', '1', 'AFAP', '2021', 'TestAddr1', 'TestAddr2', 'NewJordi', 'USA', '[email protected]', '(961)062-1234', '(588)148-1234', '75791', 'NY', 'M', 'false', 0, 'Both', 'NY', '1000', '100', 'New Hire', '8', '2021-02-01', 'M', 'Salary', '1', '0', '0', 5, 'S', 'AFAP', 'AZ', '2019', '2021-02-01', 'New Hire', '2021-02-01', 'A', '2021-02-01', true, 'NY', 'W2', '78FraleighStreet', 'RedHook', 'USA', '(276)369-1234', '12571', 'NY', 'Jr.', true, 'AdditionalRates#TEMP')
Following is an example of how to Update a Employee table:
UPDATE Employee SET PriorLastName = 'PriorLastName', [CF_PayrollAndHR_Full Computer Access] = true WHERE EmployeeId = '123'
| Name | Type | ReadOnly | References | Description |
| EmployeeId [KEY] | String | False |
Leave blank to have Web Pay automatically assign the next available employee ID. | |
| PreferredName | String | False |
Employee preferred display name. | |
| FirstName | String | False |
Employee first name. | |
| LastName | String | False |
Employee last name. | |
| MiddleName | String | False |
Employee middle name. | |
| WebTimeChargeRate | Decimal | False |
Rate to be charged to third party for time worked by the employee. It is most commonly referenced in the Cost Center Charge, Cost Center Charge vs. Cost Reports, and the Customer Invoice time and attendance reports. Decimal (12,2) | |
| WebTimeIsTimeLaborEnabled | Bool | False |
If set to true, changes to employee data will be reflected in Web Time. | |
| WebTimeBadgeNumber | String | False |
Badge number usually issued for time and attendance system use. | |
| WorkAddressCountry | String | False |
Country. | |
| WorkAddressAddress1 | String | False |
1st address line. | |
| WorkAddressPager | String | False |
Employee pager number. | |
| WorkAddressState | String | False |
State or province. | |
| WorkAddressMailStop | String | False |
Employee mail stop. | |
| WorkAddressEmailAddress | String | False |
Email. | |
| WorkAddressCity | String | False |
City. | |
| WorkAddressPhoneExtension | String | False |
Phone number extension. | |
| WorkAddressLocation | String | False |
Work Location name. | |
| WorkAddressPostalCode | String | False |
Postal code. | |
| WorkAddressCounty | String | False |
County. | |
| WorkAddressAddress2 | String | False |
2nd address line. | |
| WorkAddressMobilePhone | String | False |
Mobile phone number. | |
| WorkAddressPhone | String | False |
Phone number. | |
| Currency | String | False |
Employee is paid in this currency. | |
| EmergencyContacts | String | False |
Add or update Emergency Contacts. | |
| OwnerPercent | Decimal | False |
Percentage of employee's ownership in the company, entered as a whole number. Decimal (12,2) | |
| CustomTextFields | String | False |
Up to 8 custom fields of text type value. | |
| NonPrimaryStateTaxExemptions | Decimal | False |
State tax exemptions value.Decimal (12,2) | |
| NonPrimaryStateTaxOtherIncomeAmount | Decimal | False |
Box 4(a) on form W4 (year 2020 or later): Other income amount. Decimal (12,2) | |
| NonPrimaryStateTaxAmount | Decimal | False |
State tax code. | |
| NonPrimaryStateTaxDependentsAmount | Decimal | False |
Box 3 on form W4 (year 2020 or later): Total dependents amount. Decimal (12,2) | |
| NonPrimaryStateTaxDeductionsAmount | Decimal | False |
Box 4(b) on form W4 (year 2020 or later): Deductions amount. Decimal (12,2) | |
| NonPrimaryStateTaxTaxCalculationCode | String | False |
Tax calculation code. Common values are *F* (Flat), *P* (Percentage), *FDFP* (Flat Dollar Amount plus Fixed Percentage). | |
| NonPrimaryStateTaxPercentage | Decimal | False |
State Tax percentage. Decimal (12,2) | |
| NonPrimaryStateTaxW4FormYear | Int | False |
The state W4 form year Integer | |
| NonPrimaryStateTaxExemptions2 | Decimal | False |
State tax exemptions 2 value.Decimal (12,2) | |
| NonPrimaryStateTaxFilingStatus | String | False |
Employee state tax filing status. Common values are *S* (Single), *M* (Married). | |
| NonPrimaryStateTaxHigherRate | Bool | False |
Box 2(c) on form W4 (year 2020 or later): Multiple Jobs or Spouse Works. Boolean | |
| NonPrimaryStateTaxTaxCode | String | False |
State tax code. | |
| NonPrimaryStateTaxReciprocityCode | String | False |
Non-primary state tax reciprocity code. | |
| NonPrimaryStateTaxSpecialCheckCalc | String | False |
Supplemental check calculation code. Common values are *Blocked* (Taxes blocked on Supplemental checks), *Supp* (Use supplemental Tax Rate-Code). | |
| DepartmentPositionPositionCode | String | False |
Employee position code. Must match Company setup. | |
| DepartmentPositionShift | String | False |
Employee work shift. | |
| DepartmentPositionCostCenter1 | String | False |
Employer defined location, like *branch, division, department*, etc. Must match Company setup. | |
| DepartmentPositionIsSupervisorReviewer | Bool | False |
Indicates if employee is a supervisor or reviewer. | |
| DepartmentPositionIsUnionDuesCollected | Bool | False |
Indicates if union dues are collected. | |
| DepartmentPositionIsMinimumWageExempt | Bool | False |
Indicates if employee is exempt from minimum wage. | |
| DepartmentPositionUnionCode | String | False |
Employee union code. Must match Company setup. | |
| DepartmentPositionSupervisorCompanyNumber | String | False |
Supervisor's company number. Defaults to employee company number. | |
| DepartmentPositionJobTitle | String | False |
Employee current job title. | |
| DepartmentPositionUnionPosition | String | False |
Employee union position. Must match Company setup. | |
| DepartmentPositionCostCenter2 | String | False |
Employer defined location, like *branch, division, department*, etc. Must match Company setup. | |
| DepartmentPositionIsOvertimeExempt | Bool | False |
Indicates if employee is exempt from overtime. | |
| DepartmentPositionEffectiveDate | Date | False |
The date the position takes effect. Common formats include *MM-DD-CCYY*, *CCYY-MM-DD*. | |
| DepartmentPositionCostCenter3 | String | False |
Employer defined location, like *branch, division, department*, etc. Must match Company setup. | |
| DepartmentPositionEqualEmploymentOpportunityClass | String | False |
Values are configured in Company > Setup > HR > EEO Classes. | |
| DepartmentPositionClockBadgeNumber | String | False |
Employee clock badge number. Defaults to employeeId. | |
| DepartmentPositionReviewerEmployeeId | String | False |
Employee id of the reviewer. | |
| DepartmentPositionTipped | String | False |
Indicates if employee receives tips. | |
| DepartmentPositionReviewerCompanyNumber | String | False |
Company number of reviewer. | |
| DepartmentPositionIsUnionInitiationCollected | Bool | False |
Indicates if initiations fees are collected. | |
| DepartmentPositionSupervisorEmployeeId | String | False |
EmployeeId of the supervisor. | |
| DepartmentPositionChangeReason | String | False |
Employee department/position change reason. Must match Company setup. | |
| DepartmentPositionEmployeeType | String | False |
Employee current employment type. Common values *RFT (Regular Full Time), RPT (Regular Part Time), SNL (Seasonal), TFT (Temporary Full Time), TPT (Temporary Part Time)*. | |
| DepartmentPositionWorkersCompensation | String | False |
Employee worker compensation code. Must match Company setup. | |
| DepartmentPositionUnionAffiliationDate | Date | False |
Employee union affiliation effective date. Common formats include *MM-DD-CCYY*, *CCYY-MM-DD*. | |
| DepartmentPositionPayGroup | String | False |
Employee pay group. Must match Company setup. | |
| DisabilityDescription | String | False |
Indicates if employee has disability status. | |
| Ethnicity | String | False |
Employee ethnicity. | |
| AdditionalRate | String | False |
Add Additional Rates. | |
| CustomBooleanFields | String | False |
Up to 8 custom fields of boolean (checkbox) type value. | |
| AdditionalDirectDeposit | String | False |
Add up to 19 direct deposit accounts in addition to the main direct deposit account. IMPORTANT: A direct deposit update will remove ALL existing main and additional direct deposit information in WebPay and replace with information provided on the request. GET API will not return direct deposit data. | |
| CustomDropDownFields | String | False |
Up to 8 custom fields of the dropdown type value. | |
| CompanyFEIN | String | False |
Company FEIN as defined in Web Pay, applicable with GET requests only. | |
| Suffix | String | False |
Employee name suffix. Common values are *Jr, Sr, II*. | |
| MainDirectDepositNameOnAccount | String | False |
Name on the bank account. Defaults to employee's name. | |
| MainDirectDepositRoutingNumber | String | False |
ABA Transit Routing Number, entered without dashes or spaces. | |
| MainDirectDepositBlockSpecial | Bool | False |
Indicates if direct deposit should be blocked when special check types such as Bonus are processed. | |
| MainDirectDepositIsSkipPreNote | Bool | False |
Indicates if account will not pre-note. | |
| MainDirectDepositAccountNumber | String | False |
Account number, entered without special characters and spaces. | |
| MainDirectDepositAccountType | String | False |
Account type. Valid values are *C* (Checking), *S* (Saving), *P* (Pay Card). | |
| MainDirectDepositPreNoteDate | Date | False |
Date to end the pre-note of the account. Common formats include *MM-DD-CCYY*, *CCYY-MM-DD*. | |
| WorkEligibilityIsSsnVerified | Bool | False |
Indicates if employee SSN is verified. | |
| WorkEligibilityForeignPassportNumber | String | False |
Foreign Passport Number. | |
| WorkEligibilityIsI9Verified | Bool | False |
Indicates if employee I9 is verified. | |
| WorkEligibilityAlienOrAdmissionDocumentNumber | String | False |
Employee USCIS or Admission Number. Must be 7-10 characters and may begin with an 'A' | |
| WorkEligibilityI9Notes | String | False |
Notes regarding employee's i9. | |
| WorkEligibilityVisaType | String | False |
Employee Visa type. Must match one of the system coded values. | |
| WorkEligibilityWorkAuthorization | String | False |
Employee work authorization. Must match one of the system coded values. | |
| WorkEligibilityI9DateVerified | String | False |
Common formats include *MM-DD-CCYY*, *CCYY-MM-DD*. | |
| WorkEligibilitySsnDateVerified | String | False |
The date of employer verification of employee SSN. Common formats include *MM-DD-CCYY*, *CCYY-MM-DD*. | |
| WorkEligibilityCountryOfIssuance | String | False |
If Foreign Passport number is provided, provide its country of issuance. Must match Paylocity setup. | |
| WorkEligibilityAttestedDate | Date | False |
The date the I-9 Verification form was attested by Employer or Authorized representative. Common formats are *MM-DD-CCYY, CCYY-MM-DD*. | |
| WorkEligibilityI94AdmissionNumber | String | False |
Form I-94 admission number. Must be 11 numeric characters | |
| WorkEligibilityWorkUntil | String | False |
End date of employee work eligibility. Common formats include *MM-DD-CCYY*, *CCYY-MM-DD*. | |
| WorkEligibilitySsnNotes | String | False |
Notes regarding employee's SSN. | |
| TaxSetupSitwExemptReason | String | False |
Reason code for SITW exemption. Common values are *SE* (Statutory employee), *CR* (clergy/Religious). | |
| TaxSetupSuiExemptReason | String | False |
Reason code for SUI exemption. Common values are *SE* (Statutory employee), *CR* (clergy/Religious). | |
| TaxSetupSuiState | String | False |
Employee SUI (State Unemployment Insurance) state. | |
| TaxSetupIsStatutory | Bool | False |
Indicates if employee is statutory. | |
| TaxSetupTaxDistributionCode1099R | String | False |
Employee 1099R distribution code. Common values are *7* (Normal Distribution), *F* (Charitable Gift Annuity). | |
| TaxSetupMedExemptReason | String | False |
Reason code for Medicare exemption. Common values are *501* (5019c)(3) Organization), *IC* (Independent Contractor). | |
| TaxSetupFutaExemptReason | String | False |
Reason code for FUTA exemption. Common values are *501* (5019c)(3) Organization), *IC* (Independent Contractor). | |
| TaxSetupSitwExemptNotes | String | False |
Notes for SITW exemption. | |
| TaxSetupMedExemptNotes | String | False |
Notes for Medicare exemption. | |
| TaxSetupSsExemptNotes | String | False |
Notes for Social Security exemption. | |
| TaxSetupIsEmployee943 | Bool | False |
Indicates if employee in agriculture or farming. | |
| TaxSetupIsPension | Bool | False |
Indicates if employee is eligible for pension. | |
| TaxSetupSuiExemptNotes | String | False |
Notes for SUI exemption. | |
| TaxSetupFitwExemptNotes | String | False |
Notes for FITW exemption. | |
| TaxSetupFitwExemptReason | String | False |
Reason code for FITW exemption. Common values are *SE* (Statutory employee), *CR* (clergy/Religious). | |
| TaxSetupSsExemptReason | String | False |
Reason code for Social Security exemption. Common values are *SE* (Statutory employee), *CR* (clergy/Religious). | |
| TaxSetupTaxForm | String | False |
Employee tax form for reporting income. Valid values are *W2, 1099M, 1099R*. Default is W2. | |
| TaxSetupFutaExemptNotes | String | False |
Notes for FUTA exemption. | |
| CustomDateFields | String | False |
Up to 8 custom fields of the date type value. | |
| FederalTaxHigherRate | Bool | False |
Box 2(c) on form W4 (year 2020 or later): Multiple Jobs or Spouse Works. Boolean | |
| FederalTaxDependentsAmount | Decimal | False |
Box 3 on form W4 (year 2020 or later): Total dependents amount. Decimal (12,2) | |
| FederalTaxAmount | Decimal | False |
Tax amount. Decimal (12,2) | |
| FederalTaxTaxCalculationCode | String | False |
Tax calculation code. Common values are *F* (Flat), *P* (Percentage), *FDFP* (Flat Dollar Amount plus Fixed Percentage). | |
| FederalTaxDeductionsAmount | Decimal | False |
Box 4(b) on form W4 (year 2020 or later): Deductions amount. Decimal (12,2) | |
| FederalTaxFilingStatus | String | False |
Employee federal filing status. Common values are *S* (Single), *M* (Married). | |
| FederalTaxPercentage | Decimal | False |
Tax percentage. Decimal (12,2) | |
| FederalTaxOtherIncomeAmount | Decimal | False |
Box 4(a) on form W4 (year 2020 or later): Other income amount. Decimal (12,2) | |
| FederalTaxW4FormYear | Int | False |
The federal W4 form year Integer | |
| FederalTaxExemptions | Decimal | False |
Federal tax exemptions value. Decimal (12,2) | |
| MaritalStatus | String | False |
Employee marital status. Common values *D (Divorced), M (Married), S (Single), W (Widowed)*. | |
| Ssn | String | False |
Employee social security number. Leave it blank if valid social security number not available. | |
| BenefitSetupBenefitClassEffectiveDate | Date | False |
Date when Benefit Class takes effect. Common formats include *MM-DD-CCYY*, *CCYY-MM-DD*. | |
| BenefitSetupBenefitClass | String | False |
Benefit Class code. Values are configured in Web Pay Company > Setup > Benefits > Classes. | |
| BenefitSetupBenefitSalaryEffectiveDate | Date | False |
Date when Benefit Salary takes effect. Common formats include *MM-DD-CCYY*, *CCYY-MM-DD*. | |
| BenefitSetupBenefitSalary | Decimal | False |
Salary used to configure benefits.Decimal(12,2) | |
| BenefitSetupDoNotApplyAdministrativePeriod | Bool | False |
Applicable only for HR Enhanced clients and Benefit Classes with ACA Employment Type of Full Time. | |
| BenefitSetupIsMeasureAcaEligibility | Bool | False |
Only valid for HR Enhanced clients and Benefit Classes that are ACA Employment Type of Full Time. | |
| BirthDate | Date | False |
Employee birthdate. Common formats include *MM-DD-CCYY*, *CCYY-MM-DD*. | |
| PrimaryStateTaxExemptions | Decimal | False |
State tax exemptions value.Decimal (12,2) | |
| PrimaryStateTaxFilingStatus | String | False |
Employee state tax filing status. Common values are *S* (Single), *M* (Married). | |
| PrimaryStateTaxAmount | Decimal | False |
State tax code. | |
| PrimaryStateTaxSpecialCheckCalc | String | False |
Supplemental check calculation code. Common values are *Blocked* (Taxes blocked on Supplemental checks), *Supp* (Use supplemental Tax Rate-Code). | |
| PrimaryStateTaxTaxCalculationCode | String | False |
Tax calculation code. Common values are *F* (Flat), *P* (Percentage), *FDFP* (Flat Dollar Amount plus Fixed Percentage). | |
| PrimaryStateTaxW4FormYear | Int | False |
The state W4 form year Integer | |
| PrimaryStateTaxHigherRate | Bool | False |
Box 2(c) on form W4 (year 2020 or later): Multiple Jobs or Spouse Works. Boolean | |
| PrimaryStateTaxPercentage | Decimal | False |
State Tax percentage. Decimal (12,2) | |
| PrimaryStateTaxTaxCode | String | False |
State tax code. | |
| PrimaryStateTaxExemptions2 | Decimal | False |
State tax exemptions 2 value.Decimal (12,2) | |
| PrimaryStateTaxOtherIncomeAmount | Decimal | False |
Box 4(a) on form W4 (year 2020 or later): Other income amount. Decimal (12,2) | |
| PrimaryStateTaxDeductionsAmount | Decimal | False |
Box 4(b) on form W4 (year 2020 or later): Deductions amount. Decimal (12,2) | |
| PrimaryStateTaxDependentsAmount | Decimal | False |
Box 3 on form W4 (year 2020 or later): Total dependents amount. Decimal (12,2) | |
| LocalTax | String | False |
Add, update, or delete local tax code, filing status, and exemptions including PA-PSD taxes. | |
| Gender | String | False |
Employee gender. Common values *M* (Male), *F* (Female). | |
| StatusChangeReason | String | False |
Employee status change reason. Must match Company setup. | |
| StatusAdjustedSeniorityDate | Date | False |
Adjusted seniority date. Common formats include *MM-DD-CCYY*, *CCYY-MM-DD*. | |
| StatusEffectiveDate | Date | False |
Common formats include *MM-DD-CCYY*, *CCYY-MM-DD*. | |
| StatusHireDate | Date | False |
Employee hired date. Updates to hire date are not allowed and will be ignored. Common formats include *MM-DD-CCYY*, *CCYY-MM-DD*. | |
| StatusEmployeeStatus | String | False |
Employee current work status. Common values are *A* (Active), *L* (Leave of Absence), *T* (Terminated). | |
| StatusIsEligibleForRehire | Bool | False |
Indicates if employee eligible for rehire. | |
| StatusReHireDate | Date | False |
Rehire date if employee is rehired. Updates to re-hire date are not allowed and will be ignored. Common formats are *MM-DD-CCYY, CCYY-MM-DD*. | |
| HomeAddressMobilePhone | String | False |
Mobile phone number. | |
| HomeAddressAddress1 | String | False |
1st address line. | |
| HomeAddressPostalCode | String | False |
Postal code. | |
| HomeAddressState | String | False |
State or province. | |
| HomeAddressCounty | String | False |
County. | |
| HomeAddressAddress2 | String | False |
2nd address line. | |
| HomeAddressEmailAddress | String | False |
Email. | |
| HomeAddressPhone | String | False |
Phone number. | |
| HomeAddressCity | String | False |
City. | |
| HomeAddressCountry | String | False |
Country. | |
| PriorLastName | String | False |
Prior last name if applicable. | |
| VeteranDescription | String | False |
Indicates if employee is a veteran. | |
| IsSmoker | Bool | False |
Indicates if employee is a smoker. | |
| Salutation | String | False |
Employee preferred salutation. | |
| IsHighlyCompensated | Bool | False |
Indicates if employee meets the highly compensated employee criteria. | |
| CustomNumberFields | String | False |
Up to 8 custom fields of numeric type value. | |
| PrimaryPayRateSalary | Decimal | False |
Employee gross salary per pay period used with payType Salary.Decimal (12,2) | |
| PrimaryPayRateBeginCheckDate | Date | False |
The date of the first check on which the new pay rate will appear. This value is only applicable when updating an existing employee. Common formats include *MM-DD-CCYY*, *CCYY-MM-DD*. | |
| PrimaryPayRatePayRateNote | String | False |
Pay rate notes regarding employee. | |
| PrimaryPayRateEffectiveDate | Date | False |
The date the employee's pay rate takes effect. Common formats include *MM-DD-CCYY*, *CCYY-MM-DD*. | |
| PrimaryPayRatePayType | String | False |
Employee pay type (rate code). Valid values are *Hourly* or *Salary*. | |
| PrimaryPayRateDefaultHours | Decimal | False |
Employee default hours consistently worked. If autoPayType is set to D, employee will be paid hourly base rate for the defaultHours. Decimal (12,2) | |
| PrimaryPayRateAnnualSalary | Decimal | False |
Employee annual salary.Decimal (12,2) | |
| PrimaryPayRateChangeReason | String | False |
Pay rate change reason. | |
| PrimaryPayRatePayGrade | String | False |
Employee pay grade. Must match Company setup. | |
| PrimaryPayRateIsAutoPay | Bool | False |
If set to *True*, employee will be paid automatically using deafultHours. | |
| PrimaryPayRateBaseRate | Decimal | False |
Employee base rate, used for Hourly employees. Decimal (12,2) | |
| PrimaryPayRateRatePer | String | False |
Employee base rate frequency used with payType Hourly. Common values are *Hour, Week*. Default is Hour. | |
| PrimaryPayRatePayFrequency | String | False |
Employee current pay frequency. Common values are *A (Annual), B (Bi-Weekly), D (Daily), M (Monthly), S (Semi-Monthly), Q (Quarterly), W (Weekly)*. | |
| CompanyName | String | False |
Company name as defined in Web Pay, applicable with GET requests only. | |
| CompanyId | String | True |
Id of the Company. |
To create the csv content for the CreatePayEntryImportBatch.TimeEntry using this as a TEMP Table. When the connection to Paylocity is closed, all tables names started with Input are cleared.
| Name | Type | ReadOnly | References | Description |
| EmployeeId | String | False |
Id of the Employee | |
| Det | String | False |
Identifies the type of record being imported. Use E for earning, D for deduction, or A for accrual balances. | |
| DetCode | String | False |
The earning or benefit code. This must be a code currently defined for the company. | |
| Hours | Double | False |
The number of hours worked by the employee or the used accrual hours. | |
| Amount | Integer | False |
The dollar amount to pay the employee or the available accrual hours. If an amount is entered, any information entered in the hours, rate, and rateCode fields will be ignored. | |
| TempRate | String | False |
The employee's pay rate. If no rate is entered, the system will use the employee's base rate. | |
| RateCode | String | False |
The company defined rate code used for paying the employee. If a rate code is entered, the system will ignore the value in the rate field. | |
| CostCenter1 | String | False |
Use this field to enter an override value for the first level cost center charged by the employee. | |
| CostCenter2 | String | False |
Use this field to enter an override value for the second level cost center charged by the employee. | |
| CostCenter3 | String | False |
Use this field to enter an override value for the third level cost center charged by the employee. If entering a value for CC3, also enter values for CC1 and CC2. | |
| JobCode | String | False |
This field is used to enter an override company defined job code to be charged by the employee. | |
| Shift | String | False |
This field is used to enter an override company defined shift code to be charged by the employee. | |
| BeginDate | String | False |
Begin Date associated with this line item. | |
| EndDate | String | False |
End Date associated with this line item. | |
| WorkersCompCode | String | False |
The company defined workers comp code for the work performed by the employee. | |
| TCode1 | String | False |
Not used unless directed by service bureau (State override). When used the state override entered must be different than the employees home tax code setup otherwise this will result in blank check data. | |
| TCode2 | String | False |
Not used unless directed by service bureau (Local 1 override). When used the state override entered must be different than the employees home tax code setup otherwise this will result in blank check data. | |
| TCode3 | String | False |
Not used unless directed by service bureau (Local 2 override). When used the state override entered must be different than the employees home tax code setup otherwise this will result in blank check data. | |
| TCode4 | String | False |
Not used unless directed by service bureau (Do not use). | |
| Sequence | String | False |
Use this field to indicate multiple checks. | |
| CheckType | String | False |
Use this field to indicate an override Check Type. | |
| CheckNumber | String | False |
Use this field to indicate an override check Number. It is only valid when Check Type is 'Manual'. Check number for regular checks is assigned during processing. |
Get local taxes by tax code. Get all local taxes. Add new local tax. Delete local tax by tax code
The Sync App will use the Paylocity API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Sync App.
For example, the following queries are processed server side:
SELECT * FROM LocalTaxes WHERE EmployeeId = '123' SELECT * FROM LocalTaxes WHERE EmployeeId = '123' AND TaxCode = 'AL-BIR1'
Following is an example of how to inserting into LocalTaxes table. For example:
INSERT INTO LocalTaxes (EmployeeId, TaxCode, FilingStatus) VALUES ('999621027', 'AL-BIR1', 'N/A')
Following is an example of how to Delete LocalTaxes from the table:
DELETE FROM LocalTaxes WHERE employeeId = '123' AND TaxCode = 'AL-BIR1'
| Name | Type | ReadOnly | References | Description |
| EmployeeId [KEY] | String | True |
Employees.EmployeeId |
Id of the Employee. |
| Exemptions | Decimal | False |
Local tax exemptions value.Decimal (12,2) | |
| Exemptions2 | Decimal | False |
Local tax exemptions 2 value.Decimal (12,2) | |
| FilingStatus | String | False |
Employee local tax filing status. Must match specific local tax setup. | |
| WorkPSD | String | False |
Work location PSD. Must match Company setup. | |
| ResidentPSD | String | False |
Resident PSD (political subdivision code) applicable in PA. Must match Company setup. | |
| TaxCode | String | False |
Local tax code. | |
| CompanyId | String | True |
Id of the Company. |
Add/update non-primary state tax
The Sync App will use the Paylocity API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Sync App.
For example, the following queries are processed server side:
SELECT * FROM NonPrimaryStateTax WHERE EmployeeId = '123'
Following is an example of how to inserting into Non-PrimaryStateTax table. For example:
INSERT INTO [NonPrimaryStateTax] (Employeeid, TaxCalculationCode, Amount, TaxCode, ReciprocityCode, FilingStatus, W4FormYear, Percentage, Exemptions) VALUES ('123', 'AFAP', 50, 'NY', 'Both', 'M', 2019, 1.5, 5)
Following is an example of how to Update a Non-PrimaryStateTax table:
UPDATE [NonPrimaryStateTax] SET Percentage = 2.5, Exemptions = 10 WHERE employeeId = '123'
| Name | Type | ReadOnly | References | Description |
| EmployeeId [KEY] | String | True |
Employees.EmployeeId |
Id of the Employee. |
| TaxCalculationCode | String | False |
Tax calculation code. Common values are *F* (Flat), *P* (Percentage), *FDFP* (Flat Dollar Amount plus Fixed Percentage). | |
| Amount | Decimal | False |
State tax code. | |
| TaxCode | String | False |
State tax code. | |
| Exemptions2 | Decimal | False |
State tax exemptions 2 value.Decimal (12,2) | |
| ReciprocityCode | String | False |
Non-primary state tax reciprocity code. | |
| FilingStatus | String | False |
Employee state tax filing status. Common values are *S* (Single), *M* (Married). | |
| SpecialCheckCalc | String | False |
Supplemental check calculation code. Common values are *Blocked* (Taxes blocked on Supplemental checks), *Supp* (Use supplemental Tax Rate-Code). | |
| W4FormYear | Int | False |
The state W4 form year Integer | |
| Percentage | Decimal | False |
State Tax percentage. Decimal (12,2) | |
| Exemptions | Decimal | False |
State tax exemptions value.Decimal (12,2) | |
| CompanyId | String | True |
Id of the Company. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| DeductionsAmount | Decimal |
Box 4(b) on form W4 (year 2020 or later): Deductions amount. Decimal (12,2), This column is for INSERT and UPDATE only. |
| HigherRate | Bool |
Box 2(c) on form W4 (year 2020 or later): Multiple Jobs or Spouse Works. Boolean, This column is for INSERT and UPDATE only. |
| OtherIncomeAmount | Decimal |
Box 4(a) on form W4 (year 2020 or later): Other income amount. Decimal (12,2), This column is for INSERT and UPDATE only. |
| DependentsAmount | Decimal |
Box 3 on form W4 (year 2020 or later): Total dependents amount. Decimal (12,2), This column is for INSERT and UPDATE only. |
Add/update primary state tax
The Sync App will use the Paylocity API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Sync App.
For example, the following queries are processed server side:
SELECT * FROM PrimaryStateTax WHERE EmployeeId = '123'
Following is an example of how to inserting into PrimaryStateTax table. For example:
INSERT INTO PrimaryStateTax (Employeeid, FilingStatus, TaxCalculationCode, Exemptions, Exemptions2, Percentage, W4FormYear, TaxCode, Amount) VALUES ('999621027', 'MS', 'AFAP', 10, 15, 5, 2019, GA, 100)
Following is an example of how to Update a PrimaryStateTax table:
UPDATE PrimaryStateTax SET Exemptions = 20, Amount = 125 WHERE employeeId = '123'
| Name | Type | ReadOnly | References | Description |
| EmployeeId [KEY] | String | True |
Employees.EmployeeId |
Id of the Employee. |
| FilingStatus | String | False |
Employee state tax filing status. Common values are *S* (Single), *M* (Married). | |
| TaxCalculationCode | String | False |
Tax calculation code. Common values are *F* (Flat), *P* (Percentage), *FDFP* (Flat Dollar Amount plus Fixed Percentage). | |
| Exemptions | Decimal | False |
State tax exemptions value.Decimal (12,2) | |
| Exemptions2 | Decimal | False |
State tax exemptions 2 value.Decimal (12,2) | |
| Percentage | Decimal | False |
State Tax percentage. Decimal (12,2) | |
| W4FormYear | Int | False |
The state W4 form year Integer | |
| TaxCode | String | False |
State tax code. | |
| SpecialCheckCalc | String | False |
Supplemental check calculation code. Common values are *Blocked* (Taxes blocked on Supplemental checks), *Supp* (Use supplemental Tax Rate-Code). | |
| Amount | Decimal | False |
State tax code. | |
| CompanyId | String | True |
Id of the Company. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description |
| DeductionsAmount | Decimal |
Box 4(b) on form W4 (year 2020 or later): Deductions amount. Decimal (12,2), This column is for INSERT and UPDATE only. |
| DependentsAmount | Decimal |
Box 3 on form W4 (year 2020 or later): Total dependents amount. Decimal (12,2), This column is for INSERT and UPDATE only. |
| OtherIncomeAmount | Decimal |
Box 4(a) on form W4 (year 2020 or later): Other income amount. Decimal (12,2), This column is for INSERT and UPDATE only. |
| HigherRate | Bool |
Box 2(c) on form W4 (year 2020 or later): Multiple Jobs or Spouse Works. Boolean, This column is for INSERT and UPDATE only. |
Gets employee sensitive data information directly from Web Pay.
The Sync App will use the Paylocity API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Sync App.
For example, the following queries are processed server side:
SELECT * FROM SensitiveData WHERE EmployeeId = '1234'
Following is an example of how to Insert into SensitiveData table.
INSERT INTO SensitiveData (EmployeeId, Disability, DisabilityClassifications, HasDisability, IsVeteran) VALUES ('1234', 'ads', 'dawd, afsc', '1', '0')
Following is an example of how to Update a SensitiveData table:
UPDATE SensitiveData SET Disability = 'ads', DisabilityClassifications = 'dawd,afsc', HasDisability = '1' WHERE EmployeeId = '1234'
| Name | Type | ReadOnly | References | Description |
| EmployeeId [KEY] | String | False |
Employees.EmployeeId |
Id of the Employee. |
| CompanyId | String | False |
Id of the Company. | |
| Disability | String | False |
Description of employee's disability or accommodation. | |
| DisabilityClassifications | String | False |
Indicates the type of disability. | |
| HasDisability | String | False |
Indicates if the employee has a disability. Values include:0 = No, 1 = Yes or 2 = Prefer not to say. | |
| Ethnicity | String | False |
Employee's legal ethnicity or race. | |
| EthnicRacialIdentities | String | False |
Employee's preferred or chosen ethnicity or race. | |
| DisplayPronouns | Boolean | False |
Specifies whether employee's preferred pronouns will be displayed to co-workers in Community, Directory, etc. Values include:0 = No or 1 = Yes. | |
| GenderIdentityDescription | String | False |
Employee's preferred or chosen gender identification. Values include:0 = No, 1 = Yes or 2 = Prefer not to say. | |
| IdentifyAsLegalGender | String | False |
Employee's self-identification of legal gender. | |
| LegalGender | String | False |
Employee's legal gender. | |
| Pronouns | String | False |
Employee's preferred or chosen pronouns. | |
| SexualOrientation | String | False |
Employee's self-identification of sexual orientation. | |
| IsVeteran | String | False |
Indicates if the employee is a veteran. Values include:0 = No, 1 = Yes or 2 = Prefer not to say. | |
| Veteran | String | False |
Employee's Veteran Notes. |
Views are similar to tables in the way that data is represented; however, views are read-only.
Queries can be executed against a view as if it were a normal table.
| Name | Description |
| CompanyCodes | Get All Company Codes |
| CustomFields | Get All Custom Fields |
| DirectDeposit | Get All Direct Deposit |
| EmployeePunchDetails | Get employee punch details. |
| Employees | Get all employee info |
| PayStatementsDetails | Get employee pay statement details data for the specified year.. Get employee pay statement details data for the specified year and check date. |
| PayStatementsSummary | Get employee pay statement summary data for the specified year.. Get employee pay statement summary data for the specified year and check date. |
Get All Company Codes
The Sync App will use the Paylocity API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Sync App.
In the case of simple SELECTs, the CodeResource value will be considered as costCenter1.
For example, the following queries are processed server side:
SELECT * FROM CompanyCodes WHERE codeResource = 'costCenter1'
| Name | Type | References | Description |
| Code | String | Code. | |
| Description | String | Description. | |
| CodeResource | String | Type of Company Code. Common values costcenter1, costcenter2, costcenter3, deductions, earnings, taxes, paygrade, positions. | |
| CompanyId | String | Id of the Company. |
Get All Custom Fields
The Sync App will use the Paylocity API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Sync App.
In the case of simple SELECTs, the Category value will be considered as PayrollAndHR.
For example, the following queries are processed server side:
SELECT * FROM CustomFields WHERE Category = 'PayrollAndHR'
| Name | Type | References | Description |
| Category | String | The custom field category. | |
| Label | String | The custom field label. | |
| Values | String | A set of values that are applicable to the custom field. | |
| Type | String | The custom field type. | |
| IsRequired | Bool | Indicates whether the custom field is required. | |
| DefaultValue | String | Specifies the default value of the custom field. | |
| CompanyId | String | Id of the Company. |
Get All Direct Deposit
The Sync App will use the Paylocity API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Sync App.
For example, the following queries are processed server side:
SELECT * FROM DirectDeposit WHERE EmployeeId = '123'
| Name | Type | References | Description |
| EmployeeId [KEY] | String |
Employees.EmployeeId | Id of the Employee. |
| AdditionalDirectDeposit | String | Additional Direct Deposits that are not the main Direct Deposit. | |
| MainDirectDepositRoutingNumber | String | ABA Transit Routing Number, entered without dashes or spaces. | |
| MainDirectDepositNameOnAccount | String | Name on the bank account. Defaults to employee's name. | |
| MainDirectDepositBlockSpecial | Bool | Indicates if direct deposit should be blocked when special check types such as Bonus are processed. | |
| MainDirectDepositAccountNumber | String | Account number, entered without special characters and spaces. | |
| MainDirectDepositIsSkipPreNote | Bool | Indicates if account will not pre-note. | |
| MainDirectDepositAccountType | String | Account type. Valid values are *C* (Checking), *S* (Saving), *P* (Pay Card). | |
| MainDirectDepositPreNoteDate | Date | Date to end the pre-note of the account. Common formats include *MM-DD-CCYY*, *CCYY-MM-DD*. | |
| CompanyId | String | Id of the Company. |
Get employee punch details.
| Name | Type | References | Description |
| EmployeeId [KEY] | String |
Employees.EmployeeId | The Id of the Employee. |
| SegmentsPunchId [KEY] | String | A unique identifier assigned to each punch or time entry, ensuring that each entry is distinct, traceable, and easily referenced for tracking purposes. | |
| CompanyId | String | The Paylocity Company Id. This is the unique value provided by Paylocity to each specific Payroll Entity. | |
| BadgeNumber | Integer | The Time and Labor badge number. | |
| RelativeStart | Datetime | The relative DateTime for the beginning of the WorkedShift in the format yyyy-MM-ddThh:mm:ss. | |
| RelativeEnd | Datetime | The relative DateTime for the end of the WorkedShift in the format yyyy-MM-ddThh:mm:ss. | |
| SegmentsOrigin | String | The associated origin of the time entry. | |
| SegmentsDate | Date | The date the worked shift segment took place. In the case of overnight shifts, this is the date these worked hours apply to in payroll and can play a role in some overtime calculations. | |
| SegmentsPunchType | String | The type of punch recorded, indicating categories such as work or lunch break. | |
| SegmentsRelativeStart | Datetime | The relative DateTime of the beginning of this segment after payroll policy rules are applied. This value is Null if the segment began with a missed punch. | |
| SegmentsRelativeEnd | Datetime | The relative DateTime of the end of this segment after payroll policy rules are applied. This value is Null if the segment ended with a missed punch. | |
| SegmentsRelativeOriginalStart | Datetime | The relative DateTimeOffset of the beginning of this segment before payroll policy rules are applied. This value is Null if the segment began with a missed punch. | |
| SegmentsRelativeOriginalEnd | Datetime | The relative DateTime of the end of this segment before payroll policy rules are applied. This value is Null if the segment ended with a missed punch. | |
| SegmentsDurationHours | Double | The total hours worked by the employee for a particular punch or time entry, reflecting the duration of their work. | |
| SegmentsEarnings | Double | The total earnings accrued by the employee for the specific punch or time entry, including wages, bonuses, or additional compensation. | |
| SegmentsCostCenters | String | A list of cost centers, at most one per cost center level, that this segment of the worked shift is allocated to. |
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
| Name | Type | Description | |
| TestFlag | Boolean | A Boolean value that, when set to 'true', returns mock data. |
Get all employee info
The Paylocity does not support any column for filtering this table. All filters will be executed client side.
| Name | Type | References | Description |
| EmployeeId [KEY] | String | Employee Id. | |
| StatusCode | String | Employee current work status. Common values are *A* (Active), *L* (Leave of Absence), *T* (Terminated). | |
| StatusTypeCode | String | Employee current work status type. | |
| CompanyId | String | Id of the Company. |
Get employee pay statement details data for the specified year.. Get employee pay statement details data for the specified year and check date.
The Sync App will use the Paylocity API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Sync App.
In the case of simple SELECT the Paylocity will return present and last year records.
For example, the following queries are processed server side:
SELECT * FROM PayStatementsDetails WHERE EmployeeId = '24' AND Year = 2019 SELECT * FROM PayStatementsDetails WHERE EmployeeId = '24' AND Year = 2019 AND CheckDate = '2019-02-01'
| Name | Type | References | Description |
| EmployeeId | String |
Employees.EmployeeId | Id of the Employee |
| CheckDate | Date | The Check Date of pay statement details data | |
| CompanyId | String | Id of the Company | |
| TransactionNumber | Long | The Transaction Number of pay statement details data | |
| DetCode | String | The Det Code of pay statement details data | |
| Det | String | The Det of pay statement details data | |
| Hours | Decimal | The Hours of pay statement details data | |
| Rate | Decimal | The Rate of pay statement details data | |
| TransactionType | String | The Transaction type of pay statement details data | |
| Year | Int | The The year for which to retrieve pay statement data | |
| Amount | Decimal | The Amount of pay statement details data | |
| DetType | String | Pay statement details related to specific deduction, earning or tax types. | |
| EligibleCompensation | Decimal | The Eligible Compensation of pay statement details data |
Get employee pay statement summary data for the specified year.. Get employee pay statement summary data for the specified year and check date.
The Sync App will use the Paylocity API to process WHERE clause conditions built with the following column and operator. The rest of the filter is executed client side within the Sync App.
In the case of simple SELECTs, the Paylocity will return records from the current and previous year.
For example, the following queries are processed server side:
SELECT * FROM PayStatementsSummary WHERE EmployeeId = '123' AND Year = 2019 SELECT * FROM PayStatementsSummary WHERE EmployeeId = '123' AND Year = 2019 AND CheckDate = '2019-02-01'
| Name | Type | References | Description |
| EmployeeId | String |
Employees.EmployeeId | Id of the Employee |
| CheckDate | Date | The Check Date of pay statement summary data | |
| CompanyId | String | Id of the Company | |
| TransactionNumber | Long | The Transaction Number of pay statement summary data | |
| BeginDate | Date | The Begin Date of pay statement summary data | |
| AutoPay | Bool | The If AutoPay is enabled pay statement summary data | |
| OvertimeDollars | Decimal | The Overtime Dollars of pay statement summary data | |
| GrossPay | Decimal | The Gross Pay of pay statement summary data | |
| NetPay | Decimal | The Net Pay of pay statement summary data | |
| Hours | Decimal | The Hours of pay statement summary data | |
| RegularHours | Decimal | The Regular Hours of pay statement summary data | |
| Process | Int | The Process of pay statement summary data | |
| CheckNumber | Int | The Check Number of pay statement summary data | |
| WorkersCompCode | String | The Workers CompCode of pay statement summary data | |
| NetCheck | Decimal | The Net Check of pay statement summary data | |
| VoucherNumber | Int | The Voucher Number of pay statement summary data | |
| DirectDepositAmount | Decimal | The Direct Deposit Amount of pay statement summary data | |
| RegularDollars | Decimal | The Regular Dollars of pay statement summary data | |
| Year | Int | The Year of pay statement summary data | |
| OvertimeHours | Decimal | The Over timeHours of pay statement summary data | |
| EndDate | Date | The EndDate of pay statement summary data |
Stored procedures are function-like interfaces that extend the functionality of the Sync App beyond simple SELECT/INSERT/UPDATE/DELETE operations with Paylocity.
Stored procedures accept a list of parameters, perform their intended function, and then return any relevant response data from Paylocity, along with an indication of whether the procedure succeeded or failed.
| Name | Description |
| CreatePayEntryImportBatch | Create or merge Pay Entry Time Tracking Batch. |
| MergePayEntryImportBatch | This is used to create or merge a batch when the Pay Entry Import Status is halted at TimeClockValidationPendingAcknowledgement. |
| OnBoardingEmployee | Onboarding API sends employee data into Paylocity Onboarding to help ensure an easy and accurate hiring process for subsequent completion into Web Pay. |
Create or merge Pay Entry Time Tracking Batch.
In order to insert into CreatePayEntryImportBatch, you must submit the TimeEntry details and a Pay Period. The TimeEntry details may be submitted via
a Temp table by first inserting to the Input_TimeEntry input only table. The Pay Period may be specified by setting the PayPeriodBeginDate, PayPeriodEndDate,
and CheckDate. Alternatively, the CalendarId may be specified. For example:
INSERT INTO Input_TimeEntry (EmployeeId, Det, DetCode, Hours, Amount, BeginDate, EndDate) VALUES (999623635, 'E', 'REG', 40.00, 30, '2021-08-08', '2021-08-14') INSERT INTO Input_TimeEntry (EmployeeId, Det, DetCode, Hours, Amount, BeginDate, EndDate) VALUES (999623636, 'E', 'REG', 40.00, 25, '2021-08-08', '2021-08-14') EXECUTE CreatePayEntryImportBatch TimeEntry = 'Input_TimeEntry#TEMP', AutoAcknowledge = 'true', BatchName = 'Test', PayPeriodBeginDate = '2021-08-15', PayPeriodEndDate = '2021-08-21', CheckDate = '2021-08-27'
To fetch the processed data information, use the below query.
SELECT * FROM LastResultInfo#TEMP
| Name | Type | Required | Description |
| TimeEntry | String | True | The CSV Time Import Data. This can be submitted by inserting to the Input_TimeEntry input only table. |
| AutoAcknowledge | Boolean | False | Use true to auto acknowledge any errors or warnings for the import, false to not auto acknowledge |
| BatchName | String | False | The name of the batch. |
| MergeBatchId | String | False | The Id of the batch to be merged. |
| CalendarId | String | False | The Calendar Id for the check date. |
| PayPeriodBeginDate | String | False | The Pay Period Begin Date in YYYY-MM-DD format. |
| PayPeriodEndDate | String | False | The Pay Period End Date in YYYY-MM-DD format. |
| CheckDate | String | False | The Pay Period Check Date in YYYY-MM-DD format. |
| Name | Type | Description |
| TimeImportFileTrackingId | String | The Id of the time import file tracking. |
| Status | String | Status of the Time Import Batch. |
| BatchId | String | The Id of the Batch. |
Creates a schema definition of a table in Paylocity.
Creates a local schema file (.rsd) from an existing table or view in the data model.
The schema file is created in the directory set in the Location connection property when this procedure is executed. You can edit the file to include or exclude columns, rename columns, or adjust column datatypes.
The Sync App checks the Location to determine if the names of any .rsd files match a table or view in the data model. If there is a duplicate, the schema file will take precedence over the default instance of this table in the data model. If a schema file is present in Location that does not match an existing table or view, a new table or view entry is added to the data model of the Sync App.
| Name | Type | Required | Description |
| TableName | String | True | The name of the table. |
| FileName | String | False | The full file path and name of the schema to generate, required if the location connection property is not set. Ex:'C:\\scripts\\Employee.rsd' |
| SimplifyNames | String | False | Whether to output simple names for columns or not. Default is to simplify. |
| Name | Type | Description |
| Result | String | Whether or not the schema was successfully downloaded. |
Gets an authentication token from Paylocity.
| Name | Type | Description |
| OAuthAccessToken | String | The access token used for communication with Paylocity. |
| ExpiresIn | String | The remaining lifetime on the access token. |
This is used to create or merge a batch when the Pay Entry Import Status is halted at TimeClockValidationPendingAcknowledgement.
For example:
EXECUTE MergePayEntryImportBatch TimeImportFileTrackingId = 'e84b3808-4477-423a-89bf-e32f58c0e685'
| Name | Type | Required | Description |
| TimeImportFileTrackingId | String | True | Id of the Time Import File Tracking. |
| Name | Type | Description |
| Message | String | Message of the create or merge batch operation. |
Onboarding API sends employee data into Paylocity Onboarding to help ensure an easy and accurate hiring process for subsequent completion into Web Pay.
EXECUTE OnBoardingEmployee FirstName = 'EmpFirstName', LastName = 'EmpLastName', BaseRate = 350.0, CostCenter1 = '100', DefaultHours = '9', EmployeeStatus = 'A', MaritalStatus = 'S'
| Name | Type | Required | Description |
| FirstName | String | True | Employee first name |
| LastName | String | True | Employee last name. |
| EmployeeId | String | False | Employee Id (optional) |
| Address1 | String | False | Employee home 1st address line. |
| Address2 | String | False | Employee home 2nd address line. |
| AutoPayType | String | False | N- employee won't automatically receive a salary or hours during payroll, D - employee will be automatically paid in defaultHours during payroll, S - employee will be automatically paid Salary amount during payroll
The allowed values are N, D, S. |
| BaseRate | Decimal | False | Employee home 2nd address line. |
| City | String | False | Employee home city. |
| CostCenter1 | String | False | Employer defined location, like *branch, division, department, etc.* Must match Company setup. |
| CostCenter2 | String | False | Employer defined location, like *branch, division, department, etc.* Must match Company setup. |
| CostCenter3 | String | False | Employer defined location, like *branch, division, department, etc.* Must match Company setup. |
| DefaultHours | Decimal | False | Employee default hours consistently worked. If autoPayType is set to D, employee will be paid hourly base rate for the defaultHours |
| EmployeeStatus | String | False | Employee current work status. Common values are *A (Active), L (Leave of Absence), T (Terminated)*. |
| EmploymentType | String | False | Employee current employment type. Common values RFT *(Regular Full Time), RPT (Regular Part Time), SNL (Seasonal), TFT (Temporary Full Time), TPT (Temporary Part Time)*. |
| FederalFilingStatus | String | False | Employee federal filing status. Common values *M (Married), S (Single)*. |
| Sex | String | False | Employee gender. Common values *M (Male), F (Female)*. |
| HireDate | Date | False | Employee hired date. Common formats are MM-DD-CCYY, CCYY-MM-DD |
| HomePhone | String | False | Employee gender. Common values *M (Male), F (Female)*. |
| MaritalStatus | String | False | Employee marital status. Common values *D (Divorced), M (Married), S (Single), W (Widowed)*. |
| PersonalMobilePhone | String | False | Employee personal mobile phone number. |
| PayFrequency | String | False | Employee current pay frequency. Common values are *A (Annual), B (Bi-Weekly), D (Daily), M (Monthly), S (Semi-Monthly), Q (Quarterly), W (Weekly)*. |
| PersonalEmailAddress | String | False | Employee personal email address. |
| PayType | String | False | Employee pay type. Valid values are *Hourly or Salary*. |
| RatePer | String | False | Employee base rate frequency used with payType Hourly. Common values are *Hour or Week*. Default is Hour. |
| Salary | Decimal | False | Employee gross salary per pay period used with payType Salary. |
| State | String | False | Employee home state. |
| Ssn | String | False | Employee social security number. Leave it blank if valid social security number not available. |
| StateFilingStatus | String | False | Employee state filing status. Common values are *M (Married), S (Single)*. |
| SuiState | String | False | Employee SUI (State Unemployment Insurance) state. |
| TaxForm | String | False | Employee tax form for reporting income. Valid values are *W2, 1099M, 1099R*. Default is W2. |
| TaxState | String | False | Employee primary tax state. |
| UserName | String | False | Required. Employer assigned username to log into Onboarding. Duplicate usernames are not allowed. Must be between 3 and 20 characters and cannot have special characters other than . (period) and _ (underscore) |
| WorkEmailAddress | String | False | Employee work email. |
| Zip | String | False | Employee home zip code. |
| Name | Type | Description |
| Status | String | Stored Procedure Execution Status |
Refreshes the OAuth access token used for authentication with Paylocity.
| Name | Type | Description |
| OAuthAccessToken | String | The access token used for communication with Paylocity. |
| ExpiresIn | String | The remaining lifetime on the access token. |
The connection string properties are the various options that can be used to establish a connection. This section provides a complete list of the options you can configure in the connection string for this provider. Click the links for further details.
For more information on establishing a connection, see Establishing a Connection.
| Property | Description |
| CompanyId | The ID of the company file. |
| CustomFieldsCategory | The custom field category in the company. |
| UseSandbox | Set to true if you you are using sandbox account. |
| RSAPublicKey | Set this to the public key shared by Paylocity. |
| Key | The secret key for the symmetric algorithm. |
| IV | The initialization vector (IV). |
| UsePayEntryAPI | Set to true if you want to access the Pay Entry API. When this property is set to true, you should specify different location for OAuthSettingsFile. |
| Property | Description |
| OAuthClientId | Specifies the client ID (also known as the consumer key) assigned to your custom OAuth application. This ID is required to identify the application to the OAuth authorization server during authentication. |
| OAuthClientSecret | Specifies the client secret assigned to your custom OAuth application. This confidential value is used to authenticate the application to the OAuth authorization server. (Custom OAuth applications only.). |
| Property | Description |
| SSLClientCert | Specifies the TLS/SSL client certificate store for SSL Client Authentication (2-way SSL). This property works in conjunction with other SSL-related properties to establish a secure connection. |
| SSLClientCertType | Specifies the type of key store containing the TLS/SSL client certificate for SSL Client Authentication. Choose from a variety of key store formats depending on your platform and certificate source. |
| SSLClientCertPassword | Specifes the password required to access the TLS/SSL client certificate store. Use this property if the selected certificate store type requires a password for access. |
| SSLClientCertSubject | Specifes the subject of the TLS/SSL client certificate to locate it in the certificate store. Use a comma-separated list of distinguished name fields, such as CN=www.server.com, C=US. The wildcard * selects the first certificate in the store. |
| SSLServerCert | Specifies the certificate to be accepted from the server when connecting using TLS/SSL. |
| Property | Description |
| FirewallType | Specifies the protocol the provider uses to tunnel traffic through a proxy-based firewall. |
| FirewallServer | Identifies the IP address, DNS name, or host name of a proxy used to traverse a firewall and relay user queries to network resources. |
| FirewallPort | Specifies the TCP port to be used for a proxy-based firewall. |
| FirewallUser | Identifies the user ID of the account authenticating to a proxy-based firewall. |
| FirewallPassword | Specifies the password of the user account authenticating to a proxy-based firewall. |
| Property | Description |
| ProxyAutoDetect | Specifies whether the provider checks your system proxy settings for existing proxy server configurations, rather than using a manually specified proxy server. |
| ProxyServer | Identifies the hostname or IP address of the proxy server through which you want to route HTTP traffic. |
| ProxyPort | Identifies the TCP port on your specified proxy server that has been reserved for routing HTTP traffic to and from the client. |
| ProxyAuthScheme | Specifies the authentication method the provider uses when authenticating to the proxy server specified in the ProxyServer connection property. |
| ProxyUser | Provides the username of a user account registered with the proxy server specified in the ProxyServer connection property. |
| ProxyPassword | Specifies the password of the user specified in the ProxyUser connection property. |
| ProxySSLType | Specifies the SSL type to use when connecting to the proxy server specified in the ProxyServer connection property. |
| ProxyExceptions | Specifies a semicolon-separated list of destination hostnames or IPs that are exempt from connecting through the proxy server set in the ProxyServer connection property. |
| Property | Description |
| LogModules | Specifies the core modules to include in the log file. Use a semicolon-separated list of module names. By default, all modules are logged. |
| Property | Description |
| Location | Specifies the location of a directory containing schema files that define tables, views, and stored procedures. Depending on your service's requirements, this may be expressed as either an absolute path or a relative path. |
| BrowsableSchemas | Optional setting that restricts the schemas reported to a subset of all available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC . |
| Tables | Optional setting that restricts the tables reported to a subset of all available tables. For example, Tables=TableA,TableB,TableC . |
| Views | Optional setting that restricts the views reported to a subset of the available tables. For example, Views=ViewA,ViewB,ViewC . |
| Property | Description |
| MaxRows | Specifies the maximum number of rows returned for queries that do not include either aggregation or GROUP BY. |
| Other | Specifies advanced connection properties for specialized scenarios. Use this property only under the guidance of our Support team to address specific issues. |
| PseudoColumns | Specifies the pseudocolumns to expose as table columns, expressed as a string in the format 'TableName=ColumnName;TableName=ColumnName'. |
| Timeout | Specifies the maximum time, in seconds, that the provider waits for a server response before throwing a timeout error. |
| UserDefinedViews | Specifies a filepath to a JSON configuration file that defines custom views. The provider automatically detects and uses the views specified in this file. |
This section provides a complete list of the Connection properties you can configure in the connection string for this provider.
| Property | Description |
| CompanyId | The ID of the company file. |
| CustomFieldsCategory | The custom field category in the company. |
| UseSandbox | Set to true if you you are using sandbox account. |
| RSAPublicKey | Set this to the public key shared by Paylocity. |
| Key | The secret key for the symmetric algorithm. |
| IV | The initialization vector (IV). |
| UsePayEntryAPI | Set to true if you want to access the Pay Entry API. When this property is set to true, you should specify different location for OAuthSettingsFile. |
The ID of the company file.
The ID of the company file.
The custom field category in the company.
Add comma separated values to set more than one custom fields category. The following is an example of a custom field category:
Set to true if you you are using sandbox account.
Set to true if you you are using sandbox account.
Set this to the public key shared by Paylocity.
Either enter the key value or complete path of the file. This is required for executing Insert and Update statements.
The secret key for the symmetric algorithm.
The AES symmetric key(base 64 encoded) encrypted with the Paylocity Public Key. Paylocity will decrypt the AES key using RSA decryption and use it to decrypt the content. It is an optional property if the IV value is not provided. In this case, the driver will generate a key internally.
The initialization vector (IV).
The AES IV (base 64 encoded) used when encrypting the content. If you have set the Key, this property is optional because the driver generates an IV internally.
Set to true if you want to access the Pay Entry API. When this property is set to true, you should specify different location for OAuthSettingsFile.
Set to true if you want to access the Pay Entry API. When this property is set to true, you should specify different location for OAuthSettingsFile.
This section provides a complete list of the OAuth properties you can configure in the connection string for this provider.
| Property | Description |
| OAuthClientId | Specifies the client ID (also known as the consumer key) assigned to your custom OAuth application. This ID is required to identify the application to the OAuth authorization server during authentication. |
| OAuthClientSecret | Specifies the client secret assigned to your custom OAuth application. This confidential value is used to authenticate the application to the OAuth authorization server. (Custom OAuth applications only.). |
Specifies the client ID (also known as the consumer key) assigned to your custom OAuth application. This ID is required to identify the application to the OAuth authorization server during authentication.
This property is required in two cases:
(When the driver provides embedded OAuth credentials, this value may already be provided by the Sync App and thus not require manual entry.)
OAuthClientId is generally used alongside other OAuth-related properties such as OAuthClientSecret and OAuthSettingsLocation when configuring an authenticated connection.
OAuthClientId is one of the key connection parameters that need to be set before users can authenticate via OAuth. You can usually find this value in your identity provider’s application registration settings. Look for a field labeled Client ID, Application ID, or Consumer Key.
While the client ID is not considered a confidential value like a client secret, it is still part of your application's identity and should be handled carefully. Avoid exposing it in public repositories or shared configuration files.
For more information on how this property is used when configuring a connection, see Establishing a Connection.
Specifies the client secret assigned to your custom OAuth application. This confidential value is used to authenticate the application to the OAuth authorization server. (Custom OAuth applications only.).
This property (sometimes called the application secret or consumer secret) is required when using a custom OAuth application in any flow that requires secure client authentication, such as web-based OAuth, service-based connections, or certificate-based authorization flows. It is not required when using an embedded OAuth application.
The client secret is used during the token exchange step of the OAuth flow, when the driver requests an access token from the authorization server. If this value is missing or incorrect, authentication fails with either an invalid_client or an unauthorized_client error.
OAuthClientSecret is one of the key connection parameters that need to be set before users can authenticate via OAuth. You can obtain this value from your identity provider when registering the OAuth application.
Notes:
For more information on how this property is used when configuring a connection, see Establishing a Connection
This section provides a complete list of the SSL properties you can configure in the connection string for this provider.
| Property | Description |
| SSLClientCert | Specifies the TLS/SSL client certificate store for SSL Client Authentication (2-way SSL). This property works in conjunction with other SSL-related properties to establish a secure connection. |
| SSLClientCertType | Specifies the type of key store containing the TLS/SSL client certificate for SSL Client Authentication. Choose from a variety of key store formats depending on your platform and certificate source. |
| SSLClientCertPassword | Specifes the password required to access the TLS/SSL client certificate store. Use this property if the selected certificate store type requires a password for access. |
| SSLClientCertSubject | Specifes the subject of the TLS/SSL client certificate to locate it in the certificate store. Use a comma-separated list of distinguished name fields, such as CN=www.server.com, C=US. The wildcard * selects the first certificate in the store. |
| SSLServerCert | Specifies the certificate to be accepted from the server when connecting using TLS/SSL. |
Specifies the TLS/SSL client certificate store for SSL Client Authentication (2-way SSL). This property works in conjunction with other SSL-related properties to establish a secure connection.
This property specifies the client certificate store for SSL Client Authentication. Use this property alongside SSLClientCertType, which defines the type of the certificate store, and SSLClientCertPassword, which specifies the password for password-protected stores. When SSLClientCert is set and SSLClientCertSubject is configured, the driver searches for a certificate matching the specified subject.
Certificate store designations vary by platform. On Windows, certificate stores are identified by names such as MY (personal certificates), while in Java, the certificate store is typically a file containing certificates and optional private keys.
The following are designations of the most common User and Machine certificate stores in Windows:
| MY | A certificate store holding personal certificates with their associated private keys. |
| CA | Certifying authority certificates. |
| ROOT | Root certificates. |
| SPC | Software publisher certificates. |
For PFXFile types, set this property to the filename. For PFXBlob types, set this property to the binary contents of the file in PKCS12 format.
Specifies the type of key store containing the TLS/SSL client certificate for SSL Client Authentication. Choose from a variety of key store formats depending on your platform and certificate source.
This property determines the format and location of the key store used to provide the client certificate. Supported values include platform-specific and universal key store formats. The available values and their usage are:
| USER - default | For Windows, this specifies that the certificate store is a certificate store owned by the current user. Note that this store type is not available in Java. |
| MACHINE | For Windows, this specifies that the certificate store is a machine store. Note that this store type is not available in Java. |
| PFXFILE | The certificate store is the name of a PFX (PKCS12) file containing certificates. |
| PFXBLOB | The certificate store is a string (base-64-encoded) representing a certificate store in PFX (PKCS12) format. |
| JKSFILE | The certificate store is the name of a Java key store (JKS) file containing certificates. Note that this store type is only available in Java. |
| JKSBLOB | The certificate store is a string (base-64-encoded) representing a certificate store in JKS format. Note that this store type is only available in Java. |
| PEMKEY_FILE | The certificate store is the name of a PEM-encoded file that contains a private key and an optional certificate. |
| PEMKEY_BLOB | The certificate store is a string (base64-encoded) that contains a private key and an optional certificate. |
| PUBLIC_KEY_FILE | The certificate store is the name of a file that contains a PEM- or DER-encoded public key certificate. |
| PUBLIC_KEY_BLOB | The certificate store is a string (base-64-encoded) that contains a PEM- or DER-encoded public key certificate. |
| SSHPUBLIC_KEY_FILE | The certificate store is the name of a file that contains an SSH-style public key. |
| SSHPUBLIC_KEY_BLOB | The certificate store is a string (base-64-encoded) that contains an SSH-style public key. |
| P7BFILE | The certificate store is the name of a PKCS7 file containing certificates. |
| PPKFILE | The certificate store is the name of a file that contains a PuTTY Private Key (PPK). |
| XMLFILE | The certificate store is the name of a file that contains a certificate in XML format. |
| XMLBLOB | The certificate store is a string that contains a certificate in XML format. |
| BCFKSFILE | The certificate store is the name of a file that contains an Bouncy Castle keystore. |
| BCFKSBLOB | The certificate store is a string (base-64-encoded) that contains a Bouncy Castle keystore. |
Specifes the password required to access the TLS/SSL client certificate store. Use this property if the selected certificate store type requires a password for access.
This property provides the password needed to open a password-protected certificate store. This property is necessary when using certificate stores that require a password for decryption, as is often recommended for PFX or JKS type stores.
If the certificate store type does not require a password, for example USER or MACHINE on Windows, this property can be left blank. Ensure that the password matches the one associated with the specified certificate store to avoid authentication errors.
Specifes the subject of the TLS/SSL client certificate to locate it in the certificate store. Use a comma-separated list of distinguished name fields, such as CN=www.server.com, C=US. The wildcard * selects the first certificate in the store.
This property determines which client certificate to load based on its subject. The Sync App searches for a certificate that exactly matches the specified subject. If no exact match is found, the Sync App looks for certificates containing the value of the subject. If no match is found, no certificate is selected.
The subject should follow the standard format of a comma-separated list of distinguished name fields and values. For example, CN=www.server.com, OU=Test, C=US. Common fields include the following:
| Field | Meaning |
| CN | Common Name. This is commonly a host name like www.server.com. |
| O | Organization |
| OU | Organizational Unit |
| L | Locality |
| S | State |
| C | Country |
| E | Email Address |
Note: If any field contains special characters, such as commas, the value must be quoted. For example: CN="Example, Inc.", C=US.
Specifies the certificate to be accepted from the server when connecting using TLS/SSL.
If you are using a TLS/SSL connection, use this property to specify the TLS/SSL certificate to be accepted from the server. If you specify a value for this property, all other certificates that are not trusted by the machine are rejected.
This property can take the following forms:
| Description | Example |
| A full PEM Certificate (example shortened for brevity) | -----BEGIN CERTIFICATE----- MIIChTCCAe4CAQAwDQYJKoZIhv......Qw== -----END CERTIFICATE----- |
| A path to a local file containing the certificate | C:\cert.cer |
| The public key (example shortened for brevity) | -----BEGIN RSA PUBLIC KEY----- MIGfMA0GCSq......AQAB -----END RSA PUBLIC KEY----- |
| The MD5 Thumbprint (hex values can also be either space- or colon-separated) | ecadbdda5a1529c58a1e9e09828d70e4 |
| The SHA1 Thumbprint (hex values can also be either space- or colon-separated) | 34a929226ae0819f2ec14b4a3d904f801cbb150d |
Note: It is possible to use '*' to signify that all certificates should be accepted, but due to security concerns this is not recommended.
This section provides a complete list of the Firewall properties you can configure in the connection string for this provider.
| Property | Description |
| FirewallType | Specifies the protocol the provider uses to tunnel traffic through a proxy-based firewall. |
| FirewallServer | Identifies the IP address, DNS name, or host name of a proxy used to traverse a firewall and relay user queries to network resources. |
| FirewallPort | Specifies the TCP port to be used for a proxy-based firewall. |
| FirewallUser | Identifies the user ID of the account authenticating to a proxy-based firewall. |
| FirewallPassword | Specifies the password of the user account authenticating to a proxy-based firewall. |
Specifies the protocol the provider uses to tunnel traffic through a proxy-based firewall.
A proxy-based firewall (or proxy firewall) is a network security device that acts as an intermediary between user requests and the resources they access. The proxy accepts the request of an authenticated user, tunnels through the firewall, and transmits the request to the appropriate server.
Because the proxy evaluates and transfers data backets on behalf of the requesting users, the users never connect directly with the servers, only with the proxy.
Note: By default, the Sync App connects to the system proxy. To disable this behavior and connect to one of the following proxy types, set ProxyAutoDetect to false.
The following table provides port number information for each of the supported protocols.
| Protocol | Default Port | Description |
| TUNNEL | 80 | The port where the Sync App opens a connection to Paylocity. Traffic flows back and forth via the proxy at this location. |
| SOCKS4 | 1080 | The port where the Sync App opens a connection to Paylocity. SOCKS 4 then passes theFirewallUser value to the proxy, which determines whether the connection request should be granted. |
| SOCKS5 | 1080 | The port where the Sync App sends data to Paylocity. If the SOCKS 5 proxy requires authentication, set FirewallUser and FirewallPassword to credentials the proxy recognizes. |
To connect to HTTP proxies, use ProxyServer and ProxyPort. To authenticate to HTTP proxies, use ProxyAuthScheme, ProxyUser, and ProxyPassword.
Identifies the IP address, DNS name, or host name of a proxy used to traverse a firewall and relay user queries to network resources.
A proxy-based firewall (or proxy firewall) is a network security device that acts as an intermediary between user requests and the resources they access. The proxy accepts the request of an authenticated user, tunnels through the firewall, and transmits the request to the appropriate server.
Because the proxy evaluates and transfers data backets on behalf of the requesting users, the users never connect directly with the servers, only with the proxy.
Specifies the TCP port to be used for a proxy-based firewall.
A proxy-based firewall (or proxy firewall) is a network security device that acts as an intermediary between user requests and the resources they access. The proxy accepts the request of an authenticated user, tunnels through the firewall, and transmits the request to the appropriate server.
Because the proxy evaluates and transfers data backets on behalf of the requesting users, the users never connect directly with the servers, only with the proxy.
Identifies the user ID of the account authenticating to a proxy-based firewall.
A proxy-based firewall (or proxy firewall) is a network security device that acts as an intermediary between user requests and the resources they access. The proxy accepts the request of an authenticated user, tunnels through the firewall, and transmits the request to the appropriate server.
Because the proxy evaluates and transfers data backets on behalf of the requesting users, the users never connect directly with the servers, only with the proxy.
Specifies the password of the user account authenticating to a proxy-based firewall.
A proxy-based firewall (or proxy firewall) is a network security device that acts as an intermediary between user requests and the resources they access. The proxy accepts the request of an authenticated user, tunnels through the firewall, and transmits the request to the appropriate server.
Because the proxy evaluates and transfers data backets on behalf of the requesting users, the users never connect directly with the servers, only with the proxy.
This section provides a complete list of the Proxy properties you can configure in the connection string for this provider.
| Property | Description |
| ProxyAutoDetect | Specifies whether the provider checks your system proxy settings for existing proxy server configurations, rather than using a manually specified proxy server. |
| ProxyServer | Identifies the hostname or IP address of the proxy server through which you want to route HTTP traffic. |
| ProxyPort | Identifies the TCP port on your specified proxy server that has been reserved for routing HTTP traffic to and from the client. |
| ProxyAuthScheme | Specifies the authentication method the provider uses when authenticating to the proxy server specified in the ProxyServer connection property. |
| ProxyUser | Provides the username of a user account registered with the proxy server specified in the ProxyServer connection property. |
| ProxyPassword | Specifies the password of the user specified in the ProxyUser connection property. |
| ProxySSLType | Specifies the SSL type to use when connecting to the proxy server specified in the ProxyServer connection property. |
| ProxyExceptions | Specifies a semicolon-separated list of destination hostnames or IPs that are exempt from connecting through the proxy server set in the ProxyServer connection property. |
Specifies whether the provider checks your system proxy settings for existing proxy server configurations, rather than using a manually specified proxy server.
When this connection property is set to True, the Sync App checks your system proxy settings for existing proxy server configurations (no need to manually supply proxy server details).
This connection property takes precedence over other proxy settings. If you want to configure the Sync App to connect to a specific proxy server, set ProxyAutoDetect to False.
To connect to an HTTP proxy, see ProxyServer. For other proxies, such as SOCKS or tunneling, see FirewallType.
Identifies the hostname or IP address of the proxy server through which you want to route HTTP traffic.
The Sync App only routes HTTP traffic through the proxy server specified in this connection property when ProxyAutoDetect is set to False.
If ProxyAutoDetect is set to True (the default), the Sync App instead routes HTTP traffic through the proxy server specified in your system proxy settings.
Identifies the TCP port on your specified proxy server that has been reserved for routing HTTP traffic to and from the client.
The Sync App only routes HTTP traffic through the ProxyServer port specified in this connection property when ProxyAutoDetect is set to False.
If ProxyAutoDetect is set to True (the default), the Sync App instead routes HTTP traffic through the proxy server port specified in your system proxy settings.
For other proxy types, see FirewallType.
Specifies the authentication method the provider uses when authenticating to the proxy server specified in the ProxyServer connection property.
Supported authentication types :
For all values other than NONE, you must also set the ProxyUser and ProxyPassword connection properties.
If you need to use another authentication type, such as SOCKS 5 authentication, see FirewallType.
Provides the username of a user account registered with the proxy server specified in the ProxyServer connection property.
The ProxyUser and ProxyPassword connection properties are used to connect and authenticate against the HTTP proxy specified in ProxyServer.
After selecting one of the available authentication types in ProxyAuthScheme, set this property as follows:
| ProxyAuthScheme Value | Value to set for ProxyUser |
| BASIC | The username of a user registered with the proxy server. |
| DIGEST | The username of a user registered with the proxy server. |
| NEGOTIATE | The username of a Windows user who is a valid user in the domain or trusted domain that the proxy server is part of, in the format user@domain or domain\user. |
| NTLM | The username of a Windows user who is a valid user in the domain or trusted domain that the proxy server is part of, in the format user@domain or domain\user. |
| NONE | Do not set the ProxyPassword connection property. |
Note: The Sync App only uses this username if ProxyAutoDetect is set to False. If ProxyAutoDetect is set to True (the default), the Sync App instead uses the username specified in your system proxy settings.
Specifies the password of the user specified in the ProxyUser connection property.
The ProxyUser and ProxyPassword connection properties are used to connect and authenticate against the HTTP proxy specified in ProxyServer.
After selecting one of the available authentication types in ProxyAuthScheme, set this property as follows:
| ProxyAuthScheme Value | Value to set for ProxyPassword |
| BASIC | The password associated with the proxy server user specified in ProxyUser. |
| DIGEST | The password associated with the proxy server user specified in ProxyUser. |
| NEGOTIATE | The password associated with the Windows user account specified in ProxyUser. |
| NTLM | The password associated with the Windows user account specified in ProxyUser. |
| NONE | Do not set the ProxyPassword connection property. |
For SOCKS 5 authentication or tunneling, see FirewallType.
Note: The Sync App only uses this password if ProxyAutoDetect is set to False. If ProxyAutoDetect is set to True (the default), the Sync App instead uses the password specified in your system proxy settings.
Specifies the SSL type to use when connecting to the proxy server specified in the ProxyServer connection property.
This property determines when to use SSL for the connection to the HTTP proxy specified by ProxyServer. You can set this connection property to the following values :
| AUTO | Default setting. If ProxyServer is set to an HTTPS URL, the Sync App uses the TUNNEL option. If ProxyServer is set to an HTTP URL, the component uses the NEVER option. |
| ALWAYS | The connection is always SSL enabled. |
| NEVER | The connection is not SSL enabled. |
| TUNNEL | The connection is made through a tunneling proxy. The proxy server opens a connection to the remote host and traffic flows back and forth through the proxy. |
Specifies a semicolon-separated list of destination hostnames or IPs that are exempt from connecting through the proxy server set in the ProxyServer connection property.
The ProxyServer is used for all addresses, except for addresses defined in this property. Use semicolons to separate entries.
Note: The Sync App uses the system proxy settings by default, without further configuration needed. If you want to explicitly configure proxy exceptions for this connection, set ProxyAutoDetect to False.
This section provides a complete list of the Logging properties you can configure in the connection string for this provider.
| Property | Description |
| LogModules | Specifies the core modules to include in the log file. Use a semicolon-separated list of module names. By default, all modules are logged. |
Specifies the core modules to include in the log file. Use a semicolon-separated list of module names. By default, all modules are logged.
The Sync App writes details about each operation it performs into the logfile specified by the Logfile connection property.
Each of these logged operations are assigned to a themed category called a module, and each module has a corresponding short code used to labels individual Sync App operations as belonging to that module.
When this connection property is set to a semicolon-separated list of module codes, only operations belonging to the specified modules are written to the logfile. Note that this only affects which operations are logged moving forward and doesn't retroactively alter the existing contents of the logfile. For example: INFO;EXEC;SSL;META;
By default, logged operations from all modules are included.
You can explicitly exclude a module by prefixing it with a "-". For example: -HTTP
To apply filters to submodules, identify them with the syntax <module name>.<submodule name>. For example, the following value causes the Sync App to only log actions belonging to the HTTP module, and further refines it to exclude actions belonging to the Res submodule of the HTTP module: HTTP;-HTTP.Res
Note that the logfile filtering triggered by the Verbosity connection property takes precedence over the filtering imposed by this connection property. This means that operations of a higher verbosity level than the level specified in the Verbosity connection property are not printed in the logfile, even if they belong to one of the modules specified in this connection property.
The available modules and submodules are:
| Module Name | Module Description | Submodules |
| INFO | General Information. Includes the connection string, product version (build number), and initial connection messages. |
|
| EXEC | Query Execution. Includes execution messages for user-written SQL queries, parsed SQL queries, and normalized SQL queries. Success/failure messages for queries and query pages appear here as well. |
|
| HTTP | HTTP protocol messages. Includes HTTP requests/responses (including POST messages), as well as Kerberos related messages. |
|
| WSDL | Messages pertaining to the generation of WSDL/XSD files. | — |
| SSL | SSL certificate messages. |
|
| AUTH | Authentication related failure/success messages. |
|
| SQL | Includes SQL transactions, SQL bulk transfer messages, and SQL result set messages. |
|
| META | Metadata cache and schema messages. |
|
| FUNC | Information related to executing SQL functions. |
|
| TCP | Incoming and outgoing raw bytes on TCP transport layer messages. |
|
| FTP | Messages pertaining to the File Transfer Protocol. |
|
| SFTP | Messages pertaining to the Secure File Transfer Protocol. |
|
| POP | Messages pertaining to data transferred via the Post Office Protocol. |
|
| SMTP | Messages pertaining to data transferred via the Simple Mail Transfer Protocol. |
|
| CORE | Messages relating to various internal product operations not covered by other modules. | — |
| DEMN | Messages related to SQL remoting. | — |
| CLJB | Messages about bulk data uploads (cloud job). |
|
| SRCE | Miscellaneous messages produced by the product that don't belong in any other module. | — |
| TRANCE | Advanced messages concerning low-level product operations. | — |
This section provides a complete list of the Schema properties you can configure in the connection string for this provider.
| Property | Description |
| Location | Specifies the location of a directory containing schema files that define tables, views, and stored procedures. Depending on your service's requirements, this may be expressed as either an absolute path or a relative path. |
| BrowsableSchemas | Optional setting that restricts the schemas reported to a subset of all available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC . |
| Tables | Optional setting that restricts the tables reported to a subset of all available tables. For example, Tables=TableA,TableB,TableC . |
| Views | Optional setting that restricts the views reported to a subset of the available tables. For example, Views=ViewA,ViewB,ViewC . |
Specifies the location of a directory containing schema files that define tables, views, and stored procedures. Depending on your service's requirements, this may be expressed as either an absolute path or a relative path.
The Location property is only needed if you want to either customize definitions (for example, change a column name, ignore a column, etc.) or extend the data model with new tables, views, or stored procedures.
If left unspecified, the default location is %APPDATA%\\CData\\Paylocity Data Provider\\Schema, where %APPDATA% is set to the user's configuration directory:
| Platform | %APPDATA% |
| Windows | The value of the APPDATA environment variable |
| Linux | ~/.config |
Optional setting that restricts the schemas reported to a subset of all available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC .
Listing all available database schemas can take extra time, thus degrading performance. Providing a list of schemas in the connection string saves time and improves performance.
Optional setting that restricts the tables reported to a subset of all available tables. For example, Tables=TableA,TableB,TableC .
Listing all available tables from some databases can take extra time, thus degrading performance. Providing a list of tables in the connection string saves time and improves performance.
If there are lots of tables available and you already know which ones you want to work with, you can use this property to restrict your viewing to only those tables. To do this, specify the tables you want in a comma-separated list. Each table should be a valid SQL identifier with any special characters escaped using square brackets, double-quotes or backticks. For example, Tables=TableA,[TableB/WithSlash],WithCatalog.WithSchema.`TableC With Space`.
Note: If you are connecting to a data source with multiple schemas or catalogs, you must specify each table you want to view by its fully qualified name. This avoids ambiguity between tables that may exist in multiple catalogs or schemas.
Optional setting that restricts the views reported to a subset of the available tables. For example, Views=ViewA,ViewB,ViewC .
Listing all available views from some databases can take extra time, thus degrading performance. Providing a list of views in the connection string saves time and improves performance.
If there are lots of views available and you already know which ones you want to work with, you can use this property to restrict your viewing to only those views. To do this, specify the views you want in a comma-separated list. Each view should be a valid SQL identifier with any special characters escaped using square brackets, double-quotes or backticks. For example, Views=ViewA,[ViewB/WithSlash],WithCatalog.WithSchema.`ViewC With Space`.
Note: If you are connecting to a data source with multiple schemas or catalogs, you must specify each view you want to examine by its fully qualified name. This avoids ambiguity between views that may exist in multiple catalogs or schemas.
This section provides a complete list of the Miscellaneous properties you can configure in the connection string for this provider.
| Property | Description |
| MaxRows | Specifies the maximum number of rows returned for queries that do not include either aggregation or GROUP BY. |
| Other | Specifies advanced connection properties for specialized scenarios. Use this property only under the guidance of our Support team to address specific issues. |
| PseudoColumns | Specifies the pseudocolumns to expose as table columns, expressed as a string in the format 'TableName=ColumnName;TableName=ColumnName'. |
| Timeout | Specifies the maximum time, in seconds, that the provider waits for a server response before throwing a timeout error. |
| UserDefinedViews | Specifies a filepath to a JSON configuration file that defines custom views. The provider automatically detects and uses the views specified in this file. |
Specifies the maximum number of rows returned for queries that do not include either aggregation or GROUP BY.
The default value for this property, -1, means that no row limit is enforced unless the query explicitly includes a LIMIT clause. (When a query includes a LIMIT clause, the value specified in the query takes precedence over the MaxRows setting.)
Setting MaxRows to a whole number greater than 0 ensures that queries do not return excessively large result sets by default.
This property is useful for optimizing performance and preventing excessive resource consumption when executing queries that could otherwise return very large datasets.
Specifies advanced connection properties for specialized scenarios. Use this property only under the guidance of our Support team to address specific issues.
This property allows advanced users to configure hidden properties for specialized situations, with the advice of our Support team. These settings are not required for normal use cases but can address unique requirements or provide additional functionality. To define multiple properties, use a semicolon-separated list.
Note: It is strongly recommended to set these properties only when advised by the Support team to address specific scenarios or issues.
| Property | Description |
| DefaultColumnSize | Sets the default length of string fields when the data source does not provide column length in the metadata. The default value is 2000. |
| ConvertDateTimeToGMT=True | Converts date-time values to GMT, instead of the local time of the machine. The default value is False (use local time). |
| RecordToFile=filename | Records the underlying socket data transfer to the specified file. |
Specifies the pseudocolumns to expose as table columns, expressed as a string in the format 'TableName=ColumnName;TableName=ColumnName'.
This property allows you to define which pseudocolumns the Sync App exposes as table columns.
To specify individual pseudocolumns, use the following format:
Table1=Column1;Table1=Column2;Table2=Column3
To include all pseudocolumns for all tables use:
*=*
Specifies the maximum time, in seconds, that the provider waits for a server response before throwing a timeout error.
The timeout applies to each individual communication with the server rather than the entire query or operation. For example, a query could continue running beyond 60 seconds if each paging call completes within the timeout limit.
Timeout is set to 60 seconds by default. To disable timeouts, set this property to 0.
Disabling the timeout allows operations to run indefinitely until they succeed or fail due to other conditions such as server-side timeouts, network interruptions, or resource limits on the server.
Note: Use this property cautiously to avoid long-running operations that could degrade performance or result in unresponsive behavior.
Specifies a filepath to a JSON configuration file that defines custom views. The provider automatically detects and uses the views specified in this file.
UserDefinedViews allows you to define and manage custom views through a JSON-formatted configuration file called UserDefinedViews.json. These views are automatically recognized by the Sync App and enable you to execute custom SQL queries as if they were standard database views. The JSON file defines each view as a root element with a child element called "query", which contains the SQL query for the view.
For example:
{
"MyView": {
"query": "SELECT * FROM Employee WHERE MyColumn = 'value'"
},
"MyView2": {
"query": "SELECT * FROM MyTable WHERE Id IN (1,2,3)"
}
}
You can use this property to define multiple views in a single file and specify the filepath.
For example:
UserDefinedViews=C:\Path\To\UserDefinedViews.jsonWhen you specify a view in UserDefinedViews, the Sync App only sees that view.
For further information, see User Defined Views.
LZMA from 7Zip LZMA SDK
LZMA SDK is placed in the public domain.
Anyone is free to copy, modify, publish, use, compile, sell, or distribute the original LZMA SDK code, either in source code form or as a compiled binary, for any purpose, commercial or non-commercial, and by any means.
LZMA2 from XZ SDK
Version 1.9 and older are in the public domain.
Xamarin.Forms
Xamarin SDK
The MIT License (MIT)
Copyright (c) .NET Foundation Contributors
All rights reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
NSIS 3.10
Copyright (C) 1999-2025 Contributors THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS COMMON PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.
1. DEFINITIONS
"Contribution" means:
a) in the case of the initial Contributor, the initial code and documentation distributed under this Agreement, and b) in the case of each subsequent Contributor:
i) changes to the Program, and
ii) additions to the Program;
where such changes and/or additions to the Program originate from and are distributed by that particular Contributor. A Contribution 'originates' from a Contributor if it was added to the Program by such Contributor itself or anyone acting on such Contributor's behalf. Contributions do not include additions to the Program which: (i) are separate modules of software distributed in conjunction with the Program under their own license agreement, and (ii) are not derivative works of the Program.
"Contributor" means any person or entity that distributes the Program.
"Licensed Patents " mean patent claims licensable by a Contributor which are necessarily infringed by the use or sale of its Contribution alone or when combined with the Program.
"Program" means the Contributions distributed in accordance with this Agreement.
"Recipient" means anyone who receives the Program under this Agreement, including all Contributors.
2. GRANT OF RIGHTS
a) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive, worldwide, royalty-free copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, distribute and sublicense the Contribution of such Contributor, if any, and such derivative works, in source code and object code form.
b) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive, worldwide, royalty-free patent license under Licensed Patents to make, use, sell, offer to sell, import and otherwise transfer the Contribution of such Contributor, if any, in source code and object code form. This patent license shall apply to the combination of the Contribution and the Program if, at the time the Contribution is added by the Contributor, such addition of the Contribution causes such combination to be covered by the Licensed Patents. The patent license shall not apply to any other combinations which include the Contribution. No hardware per se is licensed hereunder.
c) Recipient understands that although each Contributor grants the licenses to its Contributions set forth herein, no assurances are provided by any Contributor that the Program does not infringe the patent or other intellectual property rights of any other entity. Each Contributor disclaims any liability to Recipient for claims brought by any other entity based on infringement of intellectual property rights or otherwise. As a condition to exercising the rights and licenses granted hereunder, each Recipient hereby assumes sole responsibility to secure any other intellectual property rights needed, if any. For example, if a third party patent license is required to allow Recipient to distribute the Program, it is Recipient's responsibility to acquire that license before distributing the Program.
d) Each Contributor represents that to its knowledge it has sufficient copyright rights in its Contribution, if any, to grant the copyright license set forth in this Agreement.
3. REQUIREMENTS
A Contributor may choose to distribute the Program in object code form under its own license agreement, provided that:
a) it complies with the terms and conditions of this Agreement; and
b) its license agreement:
i) effectively disclaims on behalf of all Contributors all warranties and conditions, express and implied, including warranties or conditions of title and non-infringement, and implied warranties or conditions of merchantability and fitness for a particular purpose;
ii) effectively excludes on behalf of all Contributors all liability for damages, including direct, indirect, special, incidental and consequential damages, such as lost profits;
iii) states that any provisions which differ from this Agreement are offered by that Contributor alone and not by any other party; and
iv) states that source code for the Program is available from such Contributor, and informs licensees how to obtain it in a reasonable manner on or through a medium customarily used for software exchange.
When the Program is made available in source code form:
a) it must be made available under this Agreement; and
b) a copy of this Agreement must be included with each copy of the Program.
Contributors may not remove or alter any copyright notices contained within the Program.
Each Contributor must identify itself as the originator of its Contribution, if any, in a manner that reasonably allows subsequent Recipients to identify the originator of the Contribution.
4. COMMERCIAL DISTRIBUTION
Commercial distributors of software may accept certain responsibilities with respect to end users, business partners and the like. While this license is intended to facilitate the commercial use of the Program, the Contributor who includes the Program in a commercial product offering should do so in a manner which does not create potential liability for other Contributors. Therefore, if a Contributor includes the Program in a commercial product offering, such Contributor ("Commercial Contributor") hereby agrees to defend and indemnify every other Contributor ("Indemnified Contributor") against any losses, damages and costs (collectively "Losses") arising from claims, lawsuits and other legal actions brought by a third party against the Indemnified Contributor to the extent caused by the acts or omissions of such Commercial Contributor in connection with its distribution of the Program in a commercial product offering. The obligations in this section do not apply to any claims or Losses relating to any actual or alleged intellectual property infringement. In order to qualify, an Indemnified Contributor must: a) promptly notify the Commercial Contributor in writing of such claim, and b) allow the Commercial Contributor to control, and cooperate with the Commercial Contributor in, the defense and any related settlement negotiations. The Indemnified Contributor may participate in any such claim at its own expense.
For example, a Contributor might include the Program in a commercial product offering, Product X. That Contributor is then a Commercial Contributor. If that Commercial Contributor then makes performance claims, or offers warranties related to Product X, those performance claims and warranties are such Commercial Contributor's responsibility alone. Under this section, the Commercial Contributor would have to defend claims against the other Contributors related to those performance claims and warranties, and if a court requires any other Contributor to pay any damages as a result, the Commercial Contributor must pay those damages.
5. NO WARRANTY
EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely responsible for determining the appropriateness of using and distributing the Program and assumes all risks associated with its exercise of rights under this Agreement, including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, programs or equipment, and unavailability or interruption of operations.
6. DISCLAIMER OF LIABILITY
EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
7. GENERAL
If any provision of this Agreement is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of the terms of this Agreement, and without further action by the parties hereto, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable.
If Recipient institutes patent litigation against a Contributor with respect to a patent applicable to software (including a cross-claim or counterclaim in a lawsuit), then any patent licenses granted by that Contributor to such Recipient under this Agreement shall terminate as of the date such litigation is filed. In addition, if Recipient institutes patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Program itself (excluding combinations of the Program with other software or hardware) infringes such Recipient's patent(s), then such Recipient's rights granted under Section 2(b) shall terminate as of the date such litigation is filed.
All Recipient's rights under this Agreement shall terminate if it fails to comply with any of the material terms or conditions of this Agreement and does not cure such failure in a reasonable period of time after becoming aware of such noncompliance. If all Recipient's rights under this Agreement terminate, Recipient agrees to cease use and distribution of the Program as soon as reasonably practicable. However, Recipient's obligations under this Agreement and any licenses granted by Recipient relating to the Program shall continue and survive.
Everyone is permitted to copy and distribute copies of this Agreement, but in order to avoid inconsistency the Agreement is copyrighted and may only be modified in the following manner. The Agreement Steward reserves the right to publish new versions (including revisions) of this Agreement from time to time. No one other than the Agreement Steward has the right to modify this Agreement. IBM is the initial Agreement Steward. IBM may assign the responsibility to serve as the Agreement Steward to a suitable separate entity. Each new version of the Agreement will be given a distinguishing version number. The Program (including Contributions) may always be distributed subject to the version of the Agreement under which it was received. In addition, after a new version of the Agreement is published, Contributor may elect to distribute the Program (including its Contributions) under the new version. Except as expressly stated in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to the intellectual property of any Contributor under this Agreement, whether expressly, by implication, estoppel or otherwise. All rights in the Program not expressly granted under this Agreement are reserved.
This Agreement is governed by the laws of the State of New York and the intellectual property laws of the United States of America. No party to this Agreement will bring a legal action under this Agreement more than one year after the cause of action arose. Each party waives its rights to a jury trial in any resulting litigation.