51

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...

Read more...

1 Comments

Read more... 1 Comments

Category: Integrations (18)

STATUS DETAILS
Under Review
Ideas Administrator
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.
41

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...

Read more...

2 Comments

Read more... 2 Comments

Category: Integrations (18)

STATUS DETAILS
Under Review
Ideas Administrator
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.
21

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...

Read more...

1 Comments

Read more... 1 Comments

Category: Integrations (18)

STATUS DETAILS
Under Review
Ideas Administrator
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.
12

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...

Read more...

0 Comments

Read more... 0 Comments

Category: Integrations (18)

STATUS DETAILS
Needs Votes
Ideas 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.

11

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...

Read more...

0 Comments

Read more... 0 Comments

Category: Integrations (18)

STATUS DETAILS
Under Review
Ideas Administrator
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.
9

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...

Read more...

0 Comments

Read more... 0 Comments

Category: Integrations (18)

STATUS DETAILS
Needs Votes
Ideas 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.

9

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...

Read more...

1 Comments

Read more... 1 Comments

Category: Integrations (18)

STATUS DETAILS
Needs Votes
Ideas 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.
8

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.

Read more...

1 Comments

Read more... 1 Comments

Category: Integrations (18)

STATUS DETAILS
Under Review
Ideas Administrator
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.
8

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 as ...

Read more...

2 Comments

Read more... 2 Comments

Category: Integrations (18)

STATUS DETAILS
Under Review
Ideas Administrator
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.
7

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...

Read more...

0 Comments

Read more... 0 Comments

Category: Integrations (18)

STATUS DETAILS
Needs Votes
Ideas 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.