Financial dimensions on worker and on position
Financial dimensions, both on the worker record and on the position record, must be exposed to CDS and added to the standard integration template. Business scenario: the financial dimensions are needed in D365FO. No HR person likes the current setup where he needs to go to the HR module in D365FO...
Position hierarchy in standard integration to D365FO must use correct dates
In the CDS entity cdm_jobpositions Microsoft totally left out the effective and expiration date for the reports to position. The standard template for integration to D365FO maps the fields cdm_validfrom resp cdm_valid to both to the position details and to the position hierarchy records in D365FO...
Thank you for your suggestion. After careful consideration, we’ve decided not to proceed with this functionality at this time. With the infrastructure merge, position hierarchy infomration is now in the same database as Finance.
This posting is provided “as is” with no warranties, and confers no rights.
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.
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 Worker certificate competency (mshr_hcmworkercertificateentity) virtual entity is available in the solution.
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:
Please add all of the CoreHR Fields in the CDS
Currently, when I need to integrate CoreHR capability on CDS, we hit the limitation of the field and entity availability on the CDS. Only having a small subset of the standard CoreHR entities and fields in CDS is limiting us to be open for different integration scenario. Please make it similar to...
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.
Microsoft Flow Connector for D365 for Talent and Availability for Business Events
Dynamics 365 for Finance and Operations has a "native" connector in Microsoft Flow. A connector cor Core HR in D365 for Talent would enable many integration scenarios. Currently you can only connect to the CDS which is very limited. There are hundreds of data entities in Talent that are public...
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.
DocuRef and DocuView access through CDS
It would be very handy to have the entities DocuRef and DocuView accessible through the CDS because of the following customer scenario's: - attach eSigned performance review documents - bulk upload certificates for employees - employee sick notes
D365 F&O to D365 Talent Integrator template and/or CDS to D365 for Talent Integrator template
Currently you can use the Dynamics integrator (in the PowerApps admin center) to integrate data from Talent to Finance and Operations; however, the opposite is not true. You cannot create a connection with your own sources and destinations unless there is a template that uses those sources and...
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.
Titles
We need the HcmTitle table to be exposed to CDS. The title field is there already on the job position entity, but the value it holds is an id, that we cannot map to the title field of the position in D365FO. Business scenario is that the customer wants the employee's title to appear in the D365F...
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.
Export of entities connected to different address configuration
In D365HR address can be configured with different structures. In more detail, address format can have only Street and in user interface Street number is populated in field Street. Or it can have Street and Street number configured as separate fields. If this setup is configured in a way that on...
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.
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.
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
This posting is provided “as is” with no warranties, and confers no rights.