Microsoft Dynamics 365
Currently nearly all the fields on the worker entity has exposed history tracking and have subsequently modification dates available. However, in the UI there is also "Name History" tracking. This is not exposed as an Odata entity. Exposing this entity would allow subscribing systems to pull chan...
The field "LastnamePrefix" in the worker entity and Initials in the "People" entity are not synchronized to CDS. In some European countries such as the Netherlands or Germany, the LastnamePrefix is needed to get the proper lastname of a worker.
The initials are quite a handy field to expose in b...
Currently you can create a list of sequence in which to display "Display As" across the application. It would be convenient if instead of a combination of patterns this could be a a flow akin a business rule in CDS. This would allow administrator to set patterns programmatically.
Right now you can add custom fields in HR and sync these to CDS. However, unlike in CDS it's impossible to add calculations etc. to these fields and you need to add these custom fields manually to every environment.
In CDS it's possible to define a solution as extension to the HR solution with ...
Currently in the HR OData feed only the WorkflowWorkItems are visible. For certain integrations with other systems it's needed that the other entities are exposed to the odata API and preferably within CDS. This would allow for integration of the workflows with other systems.
Currently it's not possible for Workflows to trigger external flows/APIs. This makes integrating workflows into other systems difficult. If a Workflow could trigger an external API, HR could make use of the action system within Dynamics and the workflow could trigger other systems.
Currently all records, including expired records, are marked as Active in CDS requiring flows to mark them as inactive. It would be helpful if this was done in the integration.