ADP Workforce Now - Support syncing future-dated fields in connector
AnsweredWhich connector?:
ADP Workforce Now
Additional details:
Currently future-dated fields on records (e.g. worker.expectedStartDate, worker.expectedTerminationDate) are not synced to the destination. These fields are critical for teams that rely on forward-looking data for planning and analytics; without these fields, downstream reports only reflect current state and miss known upcoming changes.
Requested enhancement:
Enable syncing of future-dated fields from records, even if the effective date has not yet occurred, so destinations can reflect both current and planned workforce changes. This would significantly improve the usefulness of the connector for analytics and planning use cases, especially in data warehouses where historical and forward-looking views are both important.
-
Official comment
Hi Mitali,
The request to sync future-dated fields (e.g.,
worker.expectedStartDate,worker.expectedTerminationDate) in ADP Workforce Now has been reviewed. We recognize the importance of these fields for planning and analytics purposes.To proceed, we need to confirm that these fields are available in your ADP Workforce Now Worker API response. If necessary, we may reach out for source access to validate and include these fields as part of the connector enhancement. Updates will be shared as this moves forward.
Thanks,
Sandeep -
Hi Mitali,
Great news: the fields you're requesting (
expectedStartDateandexpectedTerminationDate) are already being synced by the ADP Workforce Now connector.You'll find them in the
work_assignment_historytable, which captures assignment changes including future-dated transitions. This table is linked to the mainworkertable and includes all the forward-looking data you need for planning and forecasting.If you haven't already, check your destination to confirm these fields are populated. If you run into any issues accessing or using them, please reach out and we can help troubleshoot.
Thanks,
Tom
Please sign in to leave a comment.
Comments
2 comments