ADP Workforce Now
ADP Workforce Now is a payroll and HR platform.
Features
| Feature Name | Supported | Notes |
|---|---|---|
| Capture deletes | ||
| History mode | WORK_ASSIGNMENT_HISTORY table | |
| Custom data | ||
| Data blocking | ||
| Column hashing | ||
| Re-sync | ||
| Row filtering | ||
| API configurable | API configuration | |
| Priority-first sync | ||
| Fivetran data models | ||
| Private networking | ||
| Authorization via API |
* NOTE: We also capture history for the
PERSON_HISTORYtable, but not in the usual way. This table does not contain history columns. Instead, we infer the active records based on the_fivetran_synccolumn.
Supported deployment models
We support the SaaS Deployment model for the connector.
Setup guide
Follow our step-by-step ADP Workforce Now setup guide to connect ADP Workforce Now with your destination using Fivetran connectors.
Schema information
This schema applies to all ADP Workforce Now connections.
Sync note
We perform a daily historical sync to avoid data integrity issues caused by unreliable event queues from ADP. We have observed the following issues regarding ADP event queues:
- Multiple applications can simultaneously use the ADP event queue. Once we consume an event from the queue, we delete it as per the ADP guidelines. However, we have observed that the application which reads the event from the queue first gets the event, and other applications miss the event in the queue.
- We have observed multiple instances where events were not sent from ADP, even if there was only one consumer for the event queue.
Time card delete behavior
Fivetran soft-deletes stale WORKER_TIME_CARD records during a customer-triggered historical resync by setting _fivetran_deleted = true on rows that are no longer returned by the ADP API.
Limitations:
- Delete capture does not occur during normal incremental syncs. The
_fivetran_deletedflag is only set when you trigger a resync for the connector. - Records older than 15 months are marked as deleted on resync. The ADP API only supports retrieving up to 15 months of historical time card data. During a resync, any
WORKER_TIME_CARDrecord older than this 15-month window will be marked_fivetran_deleted = true, even if those records are still valid in the source system.