Workday Human Capital Management (HCM) link
Workday HCM is a cloud-based human capital management that brings human resources (HR), recruiting, staffing, benefits administration, compensation management and related functions together in one system.
Fivetran's Workday HCM connector only supports the Compensation, Payroll, and core HCM modules.
Featureslink
Feature Name | Supported | Notes |
---|---|---|
Capture deletes | check | See Deleted rows section for details |
Custom data | ||
Data blocking | check | Column level and table level |
Column hashing | check | |
Re-sync | check | Table level |
History | ||
API configurable | check | API configuration |
Priority-first sync | ||
Fivetran data models | check | Get the transform model; Supports Quickstart data models |
Private networking |
NOTE: When you re-sync a child table, it automatically triggers a re-sync for the parent table and its associated child tables. When you select a child table that was previously deselected, you need to re-sync its parent table to backfill the data.
NOTE: For history tables, we capture records for canceled and rescinded events because the source does not provide information on the status of these events. If you do not want to see historical records corresponding to canceled/rescinded events (for example, backdating positions to a worker), you need to re-sync the relevant history tables. Re-syncing of any history table will also drop and re-sync all history tables.
NOTE: For history tables, a few changes to entities related to workers (for example, Job Profile) may impact the compensation values for a worker without generating a new worker event. To capture such changes, we will also capture the most updated version of the worker (as of the sync date) every time we sync the worker data, along with effective dates for each worker event.
Setup guidelink
Follow our step-by-step Workday HCM setup guide to connect Workday HCM with your destination using Fivetran connectors.
Sync overviewlink
Initial synclink
When you first connect a new account, Fivetran scans every table you selected and copies every row that we have permission to view. We import each table in full before moving onto the next table. Depending on the number and size of tables to be imported, the initial sync can take a while.
Updating datalink
Fivetran uses one of the following strategies to update the tables that you included in your sync:
Incrementallink
We update tables incrementally if they have a bsvc:Updated_From
, bsvc:Updated_Through
, bsvc:Effective_From
, or bsvc:Effective_Through
column. We query the data with the following parameters:
<bsvc:Transaction_Log_Criteria_Data>
<bsvc:Transaction_Date_Range_Data>
<bsvc:Updated_From>1970-01-01T16:33:18.795Z</bsvc:Updated_From>
<bsvc:Updated_Through>2023-08-10T13:15:14.366Z</bsvc:Updated_Through>
<bsvc:Effective_From>2023-08-08T13:15:14.366Z</bsvc:Effective_From>
<bsvc:Effective_Through>2023-08-10T13:15:14.366Z</bsvc:Effective_Through>
</bsvc:Transaction_Date_Range_Data>
</bsvc:Transaction_Log_Criteria_Data>
<bsvc:Transaction_Log_Criteria_Data>
<bsvc:Transaction_Date_Range_Data>
<bsvc:Updated_From>2023-08-08T13:15:14.366Z</bsvc:Updated_From>
<bsvc:Updated_Through>2023-08-10T13:15:14.366Z</bsvc:Updated_Through>
<bsvc:Effective_From>1970-01-01T16:33:18.795Z</bsvc:Effective_From>
<bsvc:Effective_Through>2023-08-10T13:15:14.366Z</bsvc:Effective_Through>
</bsvc:Transaction_Date_Range_Data>
</bsvc:Transaction_Log_Criteria_Data>
The first instance of the transaction log records any newly effective changes up to the Effective_Through
date, regardless of when the change was made. This instance includes changes that were made prior to the historical sync that have since become effective.
The second instance captures any new changes that were entered since the last sync that are effective up to the Effective_Through
date. This instance includes the backdated transactions that are effective prior to the historical sync.
Re-importlink
We re-import tables in full if they do not have a bsvc:Updated_From
, bsvc:Updated_Through
, bsvc:Effective_From
, or bsvc:Effective_Through
column. We re-import these tables once a day to avoid slowing down our syncs.
NOTE:
WORKER
,WORKER_EVENT
,JOB_PROFILE
,POSITION
and their respective child tables are synced incrementally. All other tables are once a day re-imported tables.
Deleted rowslink
We track deleted rows differently for parent tables and child tables:
- For parent tables, we capture soft deletes during re-syncs only. We do not capture deletes for these tables during normal syncs.
- For child tables, we capture hard deletes during both syncs and re-syncs.
Schema informationlink
This schema applies to all Workday Human Capital Management connectors.
To zoom, open the ERD in a new window.Configure custom and calculated fieldslink
To configure custom and calculated fields do the following:
Configure integration system link
- Log in to your Workday application.
- In the application's search box, search for 'create integration system' and then select Create Integration System.
- Enter a name for the Integration System.
- In the Template section, select New Using Template. We recommend that you use 'Core Connector: WORKER'.
- Click OK.
- In the Configure Integration Service window, select the Enable All Services checkbox.
- Go to Custom Integration Services and click +.
- Click OK.
- Make a note of the Integration System ID for this Integration System. You will need it to configure Fivetran.
- For the Integration service field, select Create > Create Integration Field Override Service.
- In the Create Integration Field Override service page, add your service name and select WORKER (or any Business Object you want to configure the custom or calculated fields on) as the Business Object.
- For the Fields section, add all the custom field names you want to add.
TIP: These fields will later be overridden to have the calculated or custom data.
- Click OK.
Map custom fields and use field overrides link
- In the search box, search for the integration system name you created above.
- Select your integration system (Should appear in More categories > Integrations).
- Select the Configure Integration Field Overrides option.
- Select your service.
NOTE: Every field is related to a Business Object that specifies what endpoint will have this custom data field. Once you select the field values, these fields will start appearing in the SOAP responses for the specific endpoints.