Power Platform Governance and Administration

After linking Microsoft Fabric and Dataverse, if you create a table on Dataverse, it will not be saved on the Azure Synapse Link side.

Therefore, from the Azure Synapse Link side, the table must be managed, and the newly created table must be manually saved as a choice.

The more tables created, the greater the burden on the user.

Therefore, we would very much like to see the introduction of a mechanism whereby tables created on Dataverse are automatically saved on the Azure Synapse Link side as well.

The Excel Export audit log for model-driven apps is only available in the production environment.

It would be more convenient if Excel Export audit logs could be used in other environments.

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.

When Microsoft is expiriencing system breaks, they should allways inform customers, not just "som known issues!

According to Microsoft Support:

______________________________________________________

Hello Thomas,  

This error that you have got is from the outage that we had all over and it is not a problem in your ORG, however it is related to package in power apps or you can say a call stack and Stephan, as you asked for an ID unfrotunatley there is no specific ID for external use as this is a known issue and as mentioned this was global issue which was fixed by PG team, now in these scenarios we don't create any specific document as these issues can happen once in a while (may be once in a year) and we just share the details with client about the outage or the work that's been done.

some known issues are reported in admin portal as well, so once you login to power platform admin centre, there is a section called as known issues, which you can always refer.

______________________________________________________

I am concerned about the lack of specific documentation or an ID that could be referenced by clients externally. 

The suggestion that such global issues might occur "once in a while" without formal documentation or public advisories does not align with the standards of accountability and professionalism we expect from you, especially given the critical nature of these services to our business operations.

According to MS public information,the only way to map table columns is to use solution explorer (classic designer).

Title:Open solution explorer

 URL:https://learn.microsoft.com/en-us/power-apps/maker/data-platform/map-entity-fields#open-solution-explorer

But according to another public information,classic app, form, and view designers are deprecated.

Title:Classic app, form, and view designers are deprecated

 URL:https://learn.microsoft.com/en-us/power-platform/important-changes-coming#classic-app-form-and-view-designers-are-deprecated

So,I hope that it will be possible to map table columns using modern designer.

It is great to allow customers to select preferred data center in each region on signup because data center alignment is mandatory for some services such as Synapse, Key Vault,...

Currently, if we would like to delete multiple model-driven apps, we need to work on them one at a time. It would be more convenient if there were a feature to delete model-driven apps at once.

Currently, there is a known limitation in how virtual entities interact with Dataverse. The RetrieveTotalRecordCount function, which is used for native Dataverse entities, does not apply to virtual entities, leading to the total record count being set to -1 in the API response, which results in the display of 5000+.

Therefore, I would suggest that this function will support for virtual entities also so that the total number of records in subgrid view of virtual tables will reflect correctly.

In Power Platform Admin Center, currently we are not able to track the progress of Backup&Restore process. It leads to several inconveniences because we are not able to know when the environment is ready to use.

Current Behavior: In Power BI Reports published to a Fabric Workspace, if “User Persisted Filters” is enabled, users’ filter selections are retained even after navigating away and returning to the report.

Request: Implement the same “User Persisted Filters” functionality for Power BI Reports embedded as DASHBOARDS in Model Driven apps.

Proposed Functionality: When a user selects page filters in an embedded Power BI DASHBOARD (e.g., Dashboard A), these filters should persist even if the user navigates to other areas/pages within the app or starts a new session. Upon returning to Dashboard A, the previously selected filters should remain applied.