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

Community

Support Syncing Future-Dated Records from Ceridian Dayforce

Answered
Cole Middlebrook User

Connector: Ceridian Dayforce

Table source: employee_time_away_from_work | TAFW

Request: Capture records with future TimeStart values during incremental syncs.

Current behavior: The connector filters the Ceridian Dayforce "GET Employee Time Away From Work" endpoint using Filter TAFW Start Date (last cursor) and Filter TAFW End Date (current sync time). Because the API appears to filter on field TimeStart, any record where the time-off is in the future is excluded.

Why it matters: TAFW records are typically entered weeks or months before the time-off occurs. Without future dates, downstream workforce planning, scheduling, and coverage forecasting can't see approved or pending time-off until it's already taking place.

Proposed options:

  • Extend the end-date window (Filter TAFW End Date) with a 12mo look-ahead horizon, or remove end date entirely.

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Official comment
    Unnikrishnan Nair Fivetranner

    Hi Cole and Aaron,
    Thank you for this clear request!
    We've confirmed that the Dayforce API's filterTAFWEndDate parameter has no API-level restriction on future dates, so extending the look-ahead window (e.g., to NOW + 12 months) looks technically straightforward to implement. 
    We'll keep you updated on this thread as we make progress.

  • Cole Middlebrook User

    Glad to hear it and looking forward to updates!