Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Ceridian Dayforce connector - Performance module tables not available (feature request) + endpoint skip warnings

Answered
Pedro Coura User

Connector name: service ceridian_dayforce

Table name: Performance module tables:PerformanceRatings, EmployeePerformanceRating, PerformanceCycle, PerformanceRatingScale

API documentation link: https://help.dayforce.com/r/documents/Dayforce-RESTful-Web-Services-Developer-Guide/REST-Services-for-Retrieving-Employee-Information

 

Additional details:

Hi Fivetran team,

Connection details: service ceridian_dayforce (Lite), connection ciliary_peerage, group blinking_pacing, destination schema mb_dayforce_source (Snowflake).

1) Feature request - Performance module tables. We need Dayforce Performance data (PerformanceRatings, EmployeePerformanceRating, PerformanceCycle, PerformanceRatingScale) in Snowflake. We verified via your public connector ERD (86 tables) that the connector does not include any Performance module tables. The employee.performance_rating column does exist but is 100% NULL across our ~7,600 employee records - as far as we can tell, Dayforce only exposes this data through the Performance module endpoints, which the connector does not call. Our Dayforce API permissions for these endpoints are already enabled on the Fivetran integration user. Questions: is Performance module support on the connector roadmap? Is there any supported workaround? If not, please register this as a feature request.

2) Endpoint skip warnings. The connection currently shows 6 warnings: PAY_CLASS, EMPLOYMENT_STATUS_REASON, PROJECT, EMPLOYEE_SCHEDULE, EARNING_STATEMENT_HEADER and ORGANIZATION_UNIT endpoint skips. Could you confirm exactly which Dayforce API permission/feature each of these requires, so we can fix them on the Dayforce side?

Thanks!



Please sign in to leave a comment.

Comments

1 comment

Date Votes
  • Official comment
    Sisan Kumar Sahu Fivetranner

    Hi Pedro,

    Thank you for submitting your feature request for the Ceridian Dayforce connector.

    Regarding point 1: We do support performance_rating. Per the documentation here (https://developers.dayforce.com/Build/API-Explorer/Employee/GET-Employee-Details.aspx), there are a couple of prerequisites to note in the doc:

    Your user role must be assigned access to the "Read Data" subfeature under HCM Anywhere > Web Services in the Features tab of System Admin > Roles.

    In addition to feature security, you'll need to enable XRefCode (and the relevant child nodes for Employee) under RESTful Services > Human Resources > Employee in the Web Services Field-Level Access tab of System Admin > Roles.

    If you continue to experience issues after enabling these, the best next step would be to reach out to the Ceridian Dayforce support team -they can advise on any additional permissions that may be required. Should the problem persist after that, please raise a support ticket, and we'll be glad to investigate.

    Regarding point 2: We do support all of the tables you mentioned. Each has a direct documentation link indicating where access needs to be enabled. ERD link : Ceridian Dayforce ERD Link

    For example, the PAY_CLASS table's redirect button (at the far right edge) leads to this page: https://developers.dayforce.com/Build/API-Explorer/Configuration/HR-Admin-Data/Pay-Classes-(1)/GET-Pay-Class-Details.aspx, which describes where these settings can be enabled. Please ensure all fields associated with the objects are enabled.

    Best regards,
    Sahu