Integrated worker, job, and position
While mastered in only one app, worker data can be synchronized across multiple Dynamics 365 apps. For example, human resources (HR) data can be mastered in Dynamics 365 Human Resources and synchronized with Dynamics 365 Commerce, Dynamics 365 Finance, and Dynamics 365 Supply Chain Management. The data is integrated seamlessly behind the scenes. The ability to integrate data about workers ensures you're working with the same data across all Dynamics 365 apps, providing you a comprehensive view of your information.
Human resources
The integration of HR data involves just mapping the HR data between finance and operations apps and customer engagement apps.
Templates
HR data includes information about employees and contractors, positions, and jobs. A collection of table maps works together during data interaction, as shown in the following table.
| Finance and operations apps | Customer engagement apps | Description |
|---|---|---|
| Compensation job function | cdm_jobfunctions | |
| Compensation job type | cdm_jobtypes | |
| Employment job functions | msdyn_employmentjobfunctions | |
| Employment per company | cdm_employments | |
| Jobs | cdm_jobs | |
| Positions V2 | cdm_jobpositions | |
| Position type | cdm_positiontypes | |
| Position worker assignments | cdm_positionworkerassignmentmaps | |
| Worker | cdm_workers | In Dynamics 365 Finance and Supply Chain Management data, workers are classified as either employees or contractors. Dataverse can also classify workers as volunteers. Volunteers become contractors when the data is transformed back into Finance and Supply Chain Management. |
Unmapped fields
During data synchronization, it's possible that either only part of the data is synced or data isn’t synced at all from finance and operations. Changes are synchronized only when mapped fields in the entity are updated. Modifying fields that are not mapped won’t sync the data.
A list of Human Resources entities and unmapped fields within those entities are listed below. Changes to these fields will not trigger dual-write.
| Entity | Unmapped fields |
|---|---|
| Worker | WorkerStatus Gender |