Dayforce Reporting
DLH.io documentation for Dayforce Reporting
Dayforce Reporting is a reports only DLH.io connector for Ceridian Dayforce. Rather than replicating the full set of Dayforce HR, payroll, and workforce management entities, this connector synchronizes only the Dayforce Legacy Reports or Analytics Reports that you choose, using your existing Dayforce reports as the data feed.
If you need the full Dayforce entity set (employees, pay, punches, schedules, and more) instead of or in addition to reports, use the Ceridian Dayforce connector.
Setup Instructions
Follow the setup steps guide for configuring your Dayforce Reporting connection to enable data to flow into your destination via DLH.
Supported Features
Here are key features supported for this connector.
| Sync Feature | Supported | Details |
|---|---|---|
| Custom Data and Development | ✓ | Ability to enhance connector upon request |
| Historical Re-Load/Load | ✓ | |
| Incremental/Delta Load | ✓ | Depends on the report's own date parameters |
| Column Selection | ✓ | |
| Column Hashing | ✓ | |
| Re-Sync Table/Entity | ✓ | Select at the table level to reload data history (on next Sync Bridge run) |
| Custom Queries | Utilizing SQL Data Query Connector | |
| Custom Data | ||
| Captures Deleted Rows | Each report run can drop and recreate its target table instead | |
| API Sync Bridge Initiation | ✓ | |
| Priority Scheduling | ✓ | Each report can be scheduled on its own days of the week |
| Private VPC/Link | ☂ | |
| DLH Data Model Available | - |
If you have any questions about these supported features please reach out to our Customer Support team.
Details on Sync Processing
For this connector, we believe the sync processing is straightforward. We've provided a number of details, steps, and other guidance here and in the setup steps guide. Be sure to also check the change log and notes page from time to time for any changes.
DLH.io connects to Dayforce using your API credentials over secure channels. This connection is read only.
Unlike most connectors, this one has no fixed list of tables. Instead, the tables available to replicate come directly from the list of reports available to your Dayforce API user, one target table per selected report.
Connecting to Your Dayforce Reporting Account
This section enumerates the options in the Credentials and Details panes in the Dayforce Reporting Connector page within DLH.io.
Credentials Pane
This pane contains fields for entering credentials to connect to your Dayforce account. The following table describes what is needed for each field:
| Field | Description |
|---|---|
| Company Id | The Company Id of the Dayforce company you are retrieving reports from. |
| User | The user name of the Dayforce API integration user used for this connection. |
| Password | The password credential for the Dayforce API integration user. |
| Environment | The Dayforce environment to connect to, for example Production or Test. |
It's a best practice to use a dedicated Dayforce API user for this connection, and to grant it access only to the reports and report categories you intend to synchronize.
Selecting Reports
After saving the connection, open the Source Schema tab. The list of available reports is stored by DLH.io so the tab opens immediately. Click Refresh to pull the latest report list from Dayforce; newly found reports are added, and reports no longer in Dayforce are marked unavailable.
Reports whose name starts with DLH_ are selected for synchronization by default. Any other report is unselected by default and can only be enabled by DLH.io support. If you need a report without the DLH_ prefix synchronized, please contact our support team via the DLH.io Support Portal.
Use the Configurations tab to:
- Switch between Legacy Reports and Analytics Reports
- Control whether a report's target table is dropped and recreated on each run, instead of appended to
- Set a per-report schedule of which days of the week it should run
Common Issues
Dayforce enforces a throttle on report retrieval, generally around 10 reports per second up to 50 reports per hour. Once the throttle threshold is met, the DLH.io Sync Bridge pauses for an hour and then continues. See Ceridian's API throttle limits for details. The amount of data returned by each report also affects how quickly this threshold is reached.
- Ensure your reports do not have required fields without default values assigned, since this prevents DLH.io from retrieving the report.
- After changing a report in Dayforce, be sure to both Apply and Save the change. It's common to forget to click Save, which leaves DLH.io unable to see the updated report parameters or options.
- Confirm the Dayforce API user has security access to the report and to the report's category, under System Admin > Roles > Features in Dayforce.
If any issues occur with the Dayforce authorization, return to the sources page in DLH.io, edit this source, and click the Authorize Your Account or Re-Authorize Your Account button. If any issues persist please contact our support team via the DLH.io Support Portal.