Workday Human Capital Management (HCM)

Workday HCM is a cloud-based human capital management platform that brings human resources (HR), recruiting, staffing, benefits administration, absence management, time tracking, compensation management and related functions together in one system.

Fivetran's Workday HCM connector only supports the following modules:

• Absence Management
• Compensation
• core HCM
• Payroll
• Performance Management
• Time Tracking

Features

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, 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.

Supported deployment models

We support the SaaS and Hybrid deployment models for the connector.

NOTE: You must have an Enterprise or Business Critical plan to use the Hybrid Deployment model.

Setup guide

Follow our step-by-step Workday HCM setup guide to connect Workday HCM with your destination using Fivetran.

Sync overview

Initial sync

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 data

Fivetran uses one of the following strategies to update the tables that you included in your sync:

• Incremental
• Re-import

Incremental

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-import

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 rows

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.

History Mode

Currently, we support history mode for WORKER_HISTORY table and its child tables. For each of these tables, we use the effective date from worker events to create the history tables. We populate the _fivetran_start column based on the effective date of a change.

Schema information

This schema applies to all Workday Human Capital Management connections.

Schema Notes

We sync personal information from the Pre-Hire and Workers endpoints into the PERSONAL_INFORMATION table. For Wrokers data, we set the value of the type column to worker and for the Pre-hire data, we set the value of this column to pre_hire. You can use the type column to query the Workers and Pre-hire data from the PERSONAL_INFORMATION table.

Configure custom and calculated fields

To configure custom and calculated fields do the following:

Configure integration system

1. Log in to your Workday application.
2. In the application's search box, search for 'create integration system' and then select Create Integration System.
3. Enter a name for the Integration System.
4. In the Template section, select New Using Template. We recommend that you use 'Core Connector: WORKER'.
5. Click OK.
6. In the Configure Integration Service window, select the Enable All Services checkbox.
7. Go to Custom Integration Services and click +.
8. Click OK.
9. Make a note of the Integration System ID for this Integration System. You will need it to configure Fivetran.
10. For the Integration service field, select Create > Create Integration Field Override Service.
11. 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.
12. 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.

13. Click OK.

Map custom fields and use field overrides

1. In the search box, search for the integration system name you created above.
2. Select your integration system (Should appear in More categories > Integrations).
3. Select the Configure Integration Field Overrides option.
4. 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.