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

Community

Connector Improvement: Dayforce Employee Properties

Answered
Zack Paulsen User

For the EMPLOYEE_PROPERTIES endpoint, Fivetran calls the Dayforce API without specifying the contextDateRangeFrom or contextDateRangeTo parameters.

When these parameters are omitted, the Dayforce REST API defaults to returning the current “as-of-today” snapshot. Historical (ended) and future-dated property records are excluded from the response, meaning the connector does not receive or load them.

Therefore, can the API be adjusted to allow for the full history of employee properties (not just those with null effective_end_date) to be loaded?  Other table API definitions, such as work_assignment, appear to contain the same contextDateRangeFrom or contextDateRangeTo parameters, and the connector is loading historical data for that table.

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Official comment
    Sisan Kumar Sahu Fivetranner

    Hi Zack,

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

    We will be starting our analysis to evaluate the feasibility of building and maintaining a high-quality Fivetran connector. As we move forward, we may reach out with additional questions or clarifications to ensure the connector aligns with your requirements and expectations.

    In the meantime, could you briefly share your primary use case for this feature?

    We appreciate your feedback and continued support - it plays a key role in shaping our roadmap.

    Best regards,
    Sahu

  • Zack Paulsen User

    There are employee properties in Dayforce that are effective dated that we would like the ability to report on for the history of our employees.  If only surfacing the current employee properties, we lose a lot of historical data in our downstream reporting.