Handling of Contractors in the Dynamics 365 HR to Ceridian Integration
There needs to be a way to eliminate Contractors in the integration between Dynamics 365 HR and Ceridian. Contractors are typically paid by other methods other than through payroll. With the current integration specifications, there is a way to ensure they don't get created in Ceridian but they...
Make it possible to create or edit data entities through the user interface
Because the application is sealed in D365 for Talent you cannot create or edit the data entities. The Talent team should do a review of the existing data entities and make entities public unless there is a strong reason not to. For example, the skills entities, the performance entities, etc. M...
User provisioning from Dynamics 365 HR to Azure Active Directory
Ability to provisioning user in Azure AD when a new employee onboard the organisation. The below link shows how it works for other HR application (workDay), need similar ability with Dynamics HR. https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/how-provisioning-works
Thanks for the suggestion. The integration between Human Resources and Azure Active Directory is on our roadmap, but we don't currently have a timeline for feature availability. We'll continue to gather votes to help us prioritize the importantance of the idea in our roadmap.
This posting is provided “as is” with no warranties, and confers no rights.
Synchronization of hierarchies from HR to FO
It would be nice to be able to synchronize the hierarchies from D365 for HR to D365 FO .
We’re pleased to announce the completion of this functionality. For more information, see Create one set of human resources capabilities within Dynamics 365. This posting is provided “as is” with no warranties, and confers no rights.
Only active position in cdm_jobposition
In other entities in the integration, future records are not sent through in the integration, I.e. an employee with a start date in the future is not sent through. However, a position with a duration activation date in the future IS sent through - but without information from the position detail...
Thank you for your suggestion. To help us in our review process, we’re requesting votes from the community to help us understand the importance of this functionality. This posting is provided “as is” with no warranties, and confers no rights.
Mapping worker person identification number with HCMPersonalIdentificationNumberEntity
1. Add additional tasks after CoreHR to FinOps template by consume "worker person identification number" in Talent and "Identification" in FinOps. 2. Add mapping for this task will found there is no PartyNumber in "worker person identification number", which is key field in "Identification" entit...
Seniority Date needs to be part of worker integration
Most other fields are available as part of the worker integration, but seniority date is not in the CDS. Seniority date is used to calculate PTO accrual in finance and needs to be available for the integration.
We’re pleased to announce the completion of this functionality. For more information, see Expand Dynamics 365 Human Resources core data in Microsoft Dataverse. This posting is provided “as is” with no warranties, and confers no rights.
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...
This functionality is available with the release of virtual entities for Human Resources in Common Data Service, which is available in the 2020 release wave 2 for Human Resources. The mshr_hcmworkerpostaladdressv2entity virtual entity includes worker addresses that are not owned by the worker.
The feature is currently in preview with general availability planned for November 2020. For more information, see the Human Resources 2020 release wave 2 plan:
Add Common Data Services location information - Office Location
Add Common Data Services location information - Office Location, this seems to be basic information that should be accessible in CDS.
We’re pleased to announce the completion of this functionality. For more information, see Expand Dynamics 365 Human Resources core data in Microsoft Dataverse. This posting is provided “as is” with no warranties, and confers no rights.
KnownAs and NameSequence fields to be added to the worker entity in CDS
We need the KnownAs and NameSequence fields to be added to the worker entity in CDS. Business scenario is that the customer uses display sequence = KnownAsSurname in Talent and this should be the same in D365FO in order for the employee and manager to see the same employee name in D365FO ESS a...
Thank you for your suggestion. We’re considering this functionality for a future release.
This posting is provided “as is” with no warranties, and confers no rights.
Administrator
Thank you for your suggestion. To help us in our review process, we’re requesting votes from the community to help us understand the importance of this functionality. This posting is provided “as is” with no warranties, and confers no rights.