Worker address - all purposes should be synchronized
As of now, only addresses of type/purpose "Home", "Business", "shipping" and "other" are synchronized from HR to CDS. However, there are other address purposes which are often used for an employee, for instance "permanent residence" - which sounds to many clients as the relevant one to determine ...
Primary position integration from Talent to FO
We are able to integrate possition worker assignment from Talent to FO by native integration, but without IsPrimary info. It is really important to send this information to FO. Just now it works like no position is set as primary so FO set asi primary position with sooner assignment date.
List of HR Fields need to be exposed in CDS Entities for Project Implementation
We have to use Odata and CDS Entities to be used in Power Automate(MS Flow) for Email notification and Approval workflow. Support ticket Reference : 120100521000001 | Fields need to be exposed in CDS List of HR Fields need to be exposed in CDS Entities for Project Implementation are as below: ...
Worker addresses created with "select other" functionality available in CDS
Currently, CDS does not offer worker addresses where the worker is not the owner. This means that in case a worker address was created by using the "select other" functionality, it is available in CDS. For our customer this address is important as this is the information where the employee is wor...
Migrate custom fields from an environment to another
It should be allowed to migrate custom fields which are created in dev environment, to the UAT environment and then to the production environment.
Gamification for D365 ERP (F&O)
Gamification is the future for most of the companies. You have a good tool for it but you just integrate it with D365 CRM (and not for D365 ERP). It would be amazing if you provide this integration so we can use this tool with all employees (not only sales/services ones) in the company, having a...
Data Integrator can't sync future or past Dates for Position Duration
It seems CDS will push out blank dates if the Job position duration is a future dated or a previously retired job position. this causes an error when syncing into D365FO which will not accept a blank date. Would be good if this worked for non currently active job positions.
Allow multiple Compensation Levels for Job Compensation to match HR
In D365HR it is possible to add multiple compensation levels for a specific job, unfortunately this is not possible in D365FO. This obviously causes issues when trying to to use Data integrator to sync data from HR to FO, would be nice if this was standardised between systems.
CDS entity for Professional Certificates
Professional certificates should be exposed to CDS and added to the standard integration template. Business scenario: Data about professional certificates will be stored in D365HR, but other third party systems will use this data for delegating various work assignments based on these certificates.
Add a document attachment entity
Currently, there is no data entity available for document attachments in Dynamics 365 Human Resources. A quite common requirement is to upload documents when migrating to Dynamics 365 HR.