This is the most common Workday integration pattern seen so far: syncing employee master data, positions, and reporting hierarchy from Workday into Microsoft Dynamics 365, using Workday as the system of record for HR.
Objects in the schema
The reference schema exposes four report-based objects for this use case, plus one nested child object:
D365 Employee
Core employee record.
Field
Description
Employee_ID
Unique employee identifier
Company
Employing company/legal entity
Cost_Center
Cost center name
Cost_Center_-_ID
Cost center ID
Hire_Date
Date of hire
Preferred_Name_-_First_Name
Preferred first name
Preferred_Name_-_Last_Name
Preferred last name
primaryWorkEmail
Primary work email address
Active
Active employment flag
Non_Active
Inactive employment flag
Active_Status
Employment status
termination_date
Termination date
term_date_on_after
Termination date on/after filter field
D365 Position Report
Position-level detail for the employee's current role.
Field
Description
Position_ID
Unique position identifier
Position
Position name/code
Business_Title
Business title shown for the position
Management_Level
Management level (e.g. Manager, IC)
Full_Name
Worker's full name
Effective_Date_for_Current_Position
When the current position became effective
Most_Rec_Pos_Change
Date of the most recent position change
Active_Status
Whether the position is currently active
D365 Position Worker Assignment
Links a worker to a position over time.
Field
Description
Employee_ID
Worker assigned to the position
Position_ID
Position being filled
Current_Position_Filled_-_Effective_Date
Effective date the position was filled
Last_Functionally_Updated
Last update timestamp
Active_Status
Whether the assignment is currently active
D365 Position Hierarchies
Reporting/management hierarchy, including a nested manager entry.
Field
Description
Position_ID
The position in the hierarchy
CF_Worker_s_manager_position_ID
Manager's position ID
Hierarchy_Type_Name
Type of hierarchy (e.g. management, supervisory)
VALIDFROM
Validity period start for this hierarchy row
VALIDTO
Validity period end for this hierarchy row
Manager_s_Position_group
Nested child object, see below
Manager_s_Position_group (nested under D365_Position_Hierarchies):
Field
Description
Manager_Pos_ID
Manager's position ID
Manager_Most_Recent_Pos_Change
Most recent change date for the manager's position
Position_ID
The subordinate position this manager entry relates to
What this covers
Together, these four objects let the integration sync:
Active and terminated/inactive employees
Organizational placement (company, cost center)
Current position and job title
Manager and reporting-line hierarchy, including history via valid-from/valid-to dates
Why this example matters as a template
This mapping is a good reference for any future Workday employee/HR sync, not just Dynamics 365. The object names are D365-specific in this instance because the reports were built for that target, but the same pattern (Employee, Position, Worker Assignment, Hierarchy) applies whether the target is Salesforce, HubSpot, or another ERP. When adapting this for a new customer or a new target system, the report names and a few target-specific fields will change, but the shape of the four objects generally will not.
Comment Editor X