<turbo-stream action="update" target="wiki_card"><template>

<h1>Workday Dynamics 365 Employee Sync</h1>
<div class="trix-content"><p>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.</p><h3>Objects in the schema</h3><p>The reference schema exposes four report-based objects for this use case, plus one nested child object:</p><h3>D365 Employee</h3><p>Core employee record.</p><p></p><figure class="attachment attachment--content"><table class="table table-bordered"><thead><tr><td>Field</td><td>Description</td></tr></thead><tbody><tr><td>Employee_ID</td><td>Unique employee identifier</td></tr><tr><td>Company</td><td>Employing company/legal entity</td></tr><tr><td>Cost_Center</td><td>Cost center name</td></tr><tr><td>Cost_Center_-_ID</td><td>Cost center ID</td></tr><tr><td>Hire_Date</td><td>Date of hire</td></tr><tr><td>Preferred_Name_-_First_Name</td><td>Preferred first name</td></tr><tr><td>Preferred_Name_-_Last_Name</td><td>Preferred last name</td></tr><tr><td>primaryWorkEmail</td><td>Primary work email address</td></tr><tr><td>Active</td><td>Active employment flag</td></tr><tr><td>Non_Active</td><td>Inactive employment flag</td></tr><tr><td>Active_Status</td><td>Employment status</td></tr><tr><td>termination_date</td><td>Termination date</td></tr><tr><td>term_date_on_after</td><td>Termination date on/after filter field</td></tr></tbody></table><figcaption class="attachment__caption"></figcaption></figure><p></p><h3>D365 Position Report</h3><p>Position-level detail for the employee's current role.</p><p></p><figure class="attachment attachment--content"><table class="table table-bordered"><thead><tr><td>Field</td><td>Description</td></tr></thead><tbody><tr><td>Position_ID</td><td>Unique position identifier</td></tr><tr><td>Position</td><td>Position name/code</td></tr><tr><td>Business_Title</td><td>Business title shown for the position</td></tr><tr><td>Management_Level</td><td>Management level (e.g. Manager, IC)</td></tr><tr><td>Full_Name</td><td>Worker's full name</td></tr><tr><td>Effective_Date_for_Current_Position</td><td>When the current position became effective</td></tr><tr><td>Most_Rec_Pos_Change</td><td>Date of the most recent position change</td></tr><tr><td>Active_Status</td><td>Whether the position is currently active</td></tr></tbody></table><figcaption class="attachment__caption"></figcaption></figure><p></p><h3>D365 Position Worker Assignment</h3><p>Links a worker to a position over time.</p><p></p><figure class="attachment attachment--content"><table class="table table-bordered"><thead><tr><td>Field</td><td>Description</td></tr></thead><tbody><tr><td>Employee_ID</td><td>Worker assigned to the position</td></tr><tr><td>Position_ID</td><td>Position being filled</td></tr><tr><td>Current_Position_Filled_-_Effective_Date</td><td>Effective date the position was filled</td></tr><tr><td>Last_Functionally_Updated</td><td>Last update timestamp</td></tr><tr><td>Active_Status</td><td>Whether the assignment is currently active</td></tr></tbody></table><figcaption class="attachment__caption"></figcaption></figure><p></p><h3>D365 Position Hierarchies</h3><p>Reporting/management hierarchy, including a nested manager entry.</p><p></p><figure class="attachment attachment--content"><table class="table table-bordered"><thead><tr><td>Field</td><td>Description</td></tr></thead><tbody><tr><td>Position_ID</td><td>The position in the hierarchy</td></tr><tr><td>CF_Worker_s_manager_position_ID</td><td>Manager's position ID</td></tr><tr><td>Hierarchy_Type_Name</td><td>Type of hierarchy (e.g. management, supervisory)</td></tr><tr><td>VALIDFROM</td><td>Validity period start for this hierarchy row</td></tr><tr><td>VALIDTO</td><td>Validity period end for this hierarchy row</td></tr><tr><td>Manager_s_Position_group</td><td>Nested child object, see below</td></tr></tbody></table><figcaption class="attachment__caption"></figcaption></figure><p></p><p><strong>Manager_s_Position_group</strong> (nested under <code>D365_Position_Hierarchies</code>):</p><p></p><figure class="attachment attachment--content"><table class="table table-bordered"><thead><tr><td>Field</td><td>Description</td></tr></thead><tbody><tr><td>Manager_Pos_ID</td><td>Manager's position ID</td></tr><tr><td>Manager_Most_Recent_Pos_Change</td><td>Most recent change date for the manager's position</td></tr><tr><td>Position_ID</td><td>The subordinate position this manager entry relates to</td></tr></tbody></table><figcaption class="attachment__caption"></figcaption></figure><p></p><h3>What this covers</h3><p>Together, these four objects let the integration sync:</p><ul><li>Active and terminated/inactive employees</li><li>Organizational placement (company, cost center)</li><li>Current position and job title</li><li>Manager and reporting-line hierarchy, including history via valid-from/valid-to dates</li></ul><h3>Why this example matters as a template</h3><p>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.</p></div>
</template></turbo-stream>

