-
Align Power Platform regions with Azure regions
When creating a new environment only a few regions can be selected. The West Europe and North Europe regions are not available. If you choose Europe - Default the environment might be provisioned in either West Europe or North Europe. Not knowing which Azure region is used is a problem when you want to export data to the Data Lake. The storage account must be in the same region as the CDS environment. If you have all Azure resources and other D365 environments in another region the data must be transferred between regions for integrations which is slower than having everything in the same region. There the regions for the D365 HR deployment must be aligned with the Azure regions. -
Allow virtual entity as trigger for flow
Currently a flow can be triggered from a change in an entity in Dataverse using the action "When a row is added, modified or deleted". But if the entity is virtual this does not work ("Virtual entities are not supported."). It should be possible to trigger a flow with a change in a virtual entity. -
Add entity "Worker personal contact person" to Dataverse
The Data Management entity "Worker personal contact person" holds data about the employee's spouse and children. This is missing in Dataverse. It can be accessed as a virtual entity in Dataverse. But changes in virtual entities cannot be used as trigger in flows. Please add the entity to Dataverse. -
Link to vendor from inventory owners form
Vendors can be selected as inventory owners when using vendor owned inventory consignment (Inventory management > Inquiries and reports > Tracking dimensions > Inventory owners). The vendor account number is displayed in the form. The field is display as a link. However, the link is not working. There should be a direct link from the Vendor account field on the form to the Vendor details form. -
Remove file size limit for backup or and restore of security configuration in User Security Governance
From the Security Category form it is possible to backup and restore the security configuration. This is useful to transfer the setup from one environment to another.
However, there seems to be a limit to the xml file size of 5.0MB. In scenarios with larger configurations this blocks the transfer of the configurations.
The limit should be removed or made adjustable.