Integration from Dynamics 365 for Talent to Dynamics 365 for Finance and Operations
This topic describes the functionality available for integration from Dynamics 365 for Talent and Dynamics 365 for Finance and Operations. The Talent to Finance and Operations template that is available with the Data Integrator enables the flow of data for jobs, positions, and workers. The data flows from Talent into Finance and Operations. The template does not provide the ability for data to flow back from Finance and Operations into Talent.
The Talent to Finance and Operations solution provides the following types of data synchronization.
- Maintain jobs in Talent and sync them from Talent to Finance and Operations.
- Maintain positions and position assignments in Talent and sync them from Talent to Finance and Operations.
- Maintain employments in Talent and sync them from Talent to Finance and Operations.
- Maintain workers and worker addresses in Talent and sync them from Talent to Finance and Operations.
System requirements for Talent
The integration solution requires the following versions of the Talent and Finance and Operations apps.
- Dynamics 365 for Talent on CDS for Apps.
- Dynamics 365 for Finance and Operations version 7.2 and later.
Template and tasks
To access the template, do the following.
- Open PowerApps Admin Center.
- Select Projects, and then, in the upper-right corner, select New project to select public templates. A new project will need to be created for each legal entity that you want to integrate into in Finance and Operations.
The following template is used to synchronize records from Talent to Finance and Operations.
Name of the template in Data integration: Core HR (Talent CDS to Fin and Ops)
The name of the task contains the entities used in each application. The source (Talent) is on the left and the destination (Finance and Operations) is on the right.
The following underlying tasks are used to synchronize records from Talent to Finance and Operations.
- Job Functions to Compensation Job Function.
- Departments to Operating Unit
- Departments to Operating Unit
- Job Types to Compensation Job Type
- Jobs to Jobs
- Jobs to Job Detail
- Position Types to Position Type
- Job Positions to Positions
- Job Positions to Positions Parent Job Assignment
- Workers to Worker
- Employments to Employment
- Employments to Employment Detail
- Position Worker Assignment to Position Worker Assignments
- Worker Addresses to Worker Postal Address V2
When integrating data from Talent to Finance and Operations, the integration will attempt to match records based on the ID. If the match occurs, the data in Finance and Operations will be overwritten with the values in Talent. However, an issue may occur if logically these are different records and the same ID was generated in either Talent or Finance and Operations based on the respective number sequence.
The areas where this can occur are Worker, which uses Personnel number to make the match, and Positions. Jobs do not use number sequences, as a result, if the same job ID is present in both Talent and Finance and Operations, the Talent information will overwrite the Finance and Operations information.
To prevent issues with duplicate IDs, you can either add a prefix on the number sequence, or set a beginning number on the number sequence that is beyond the range of the other system.
The location ID used for worker address isn't part of a number sequence. When integrating a worker address from Talent to Finance and Operations, if the worker address already exists in Finance and Operations, a duplicate address record may be created.
The following illustration shows an example of a template mapping in Data Integrator.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.