Power Platform Governance and Administration

With the current specification, the only way to customize the title is to use an event handler and specify the style in JavaScript, which is not easy to do.

Implementing the ability to change the text and background colors in the Power Apps form when a specific value is selected for a selection type item in the Dataverse table will make it easier for customers to understand and use the data when they check it.

After introducing New Look in Dynamics 365 sales and case management, the "New Look" enabled Case Type filed value is break down into multiple row. if it does not fit width of the drop down which creates confusion to the user that the value in the drop down showing as two rows for single value. In the "Old Look" value for the case type field is not break down into multiple rows even the field value length is more than the drop down width. Our customer is not happy about this design changes, we are suggesting to change the design of new look dropdown for case type as same as old look.

There is a product issue using virtual tables with OData v4 Data Sources that require an authentication header. The allowable size of the column used to store the header value is limited to 1024 characters. This was originally opened in a support ticket and was confirmed during a call with a Power Platform CSA.

We attempted to use an OAuth bearer token for authorization, but it was ~1,200 characters and was truncated when entered manually in the UI form. The documentation on request parameters led us to believe this was supported but the underlying Dataverse table called "OData v4 Data Source" has a max size of 1,024 characters for the "parameter*value" columns. We suggest the size should be increased to something larger to accommodate larger token sizes.

After introducing New Look in Dynamics 365 sales and case management, the "New Look" enabled Case Type filed value and case priority filed value is break down into multiple row. if it does not fit width of the drop down which creates confusion to the user that the value in the drop down showing as two rows for single value. In the "Old Look" value for the case type field is not break down into multiple rows even the field value length is more than the drop down width. Our customer is not happy about this design changes, we are suggesting to change the design of "New Look" dropdown's for case type and case priority as same as "Old Look".

We link D365 F&O tables to Fabric via the link to Microsoft Fabric, with microsoft onelake. When issues arise on the D365 F&O side and the link is broken, all tables will go out of sync. To fix this, we need to:

• remove all D365 tables manually (via Manage tables)
• wait for the tables to be deleted on the Fabric side (can take multiple hours)
• refresh Fabric tables
• add all d365 tables manually (via Manage tables)
• wait for the tables to be get out of initial sync
• refresh Fabric tables

This process is painful for us, we would like to be able to script those activities, so this process can happen automatically in case of table errors all across the board.

Hi !

In the Azure Synapse link page, when selecting the tables you want to synchronized, there is no way to filter the list of all the tables. This is even more obvious with the tables coming from Finance and operation. Could the table selection grid in this power app windows have the same filtering option than the F&O - export to datalake one ?

A complete filter option on the name of the table , especially the "is one of" filter would greatly ease the table selections.

Currently, all the applications will be affected if the Limit sharing setting is enabled (https://learn.microsoft.com/en-us/power-platform/admin/managed-environment-sharing-limits). We should have the option to exclude some applications.

All our tables are set to append only in our Azure Database link. After a DB refresh, we have to remove all our tables in our Azure Database link and add them back to get them to load. This is a manually intensive effort and only gets worse as we continue to add tables to our link for reporting.

Active users by device type in Dataverse analytics can't see the device name.

By implementing this feature, users can see the name of the device they are logged in to, which makes management more efficient.

As we are automating the process with help of Task Mining in Power Automate tool. After recording the video, it is providing the output as steps involved in that task mining and an analyzation part. After analyzation, can we see the recoding video again. Is there any possibility to check on that