Status Reason Transition Out of the Box error message wording bad grammar
When Status Reason Transition is applied to a table, if a user tries to set the status on a record that is not valid status transition, they are presented with an error message which is expected however the wording on the error message needs to be changed. The current wording is “Actio...
Reduce transient "No Sandbox Hosts available" failures during high-concurrency plug-in execution (batch jobs)
When a batch job triggers many sandbox plug-in executions almost simultaneously (in my case, a monthly job firing the rollup-calculation plug-in for 63 Debit Note lines at once), one record intermittently fails with: "The plug-in execution failed because no Sandbox Hosts are currently avai...
Restore the "Delete Import Source File" button to the Data iImport list view
Current state & problem
Following a recent UI update, the "Delete Import Source File" option was removed from the command bar on the Data Import list view. Users are now forced to open each individual import record to access this delete button.
While we understand ...
No Warning for Excel Export Row Limitation in CRM
When downloading an Excel file from a view in Dynamics 365 Customer Service containing over 100,000 rows, no warning message is displayed to indicate that the data might be incomplete due to the row limitation.
Error message should state clearly unmapped field since import failed.
During Dataverse data import (CSV) in the modern UCI import experience, users may hit a mapping/validation failure at the “Review Mapping” step. In some cases, the error message displayed to the user contains unreplaced placeholder tokens such as {0} and {1} (for exam...
Power Page SharePoint Integration MimeType Validation
The Power Platform admin center features a section to define valid file type extensions or mimetypes. This is used to validate files that are uploaded to a Dataverse file column or attachment table.
HOWEVER, this validation is not used at all when using the SharePoint integrat...
Lack of Native Monitoring and Failure Diagnostics for Dataverse → Microsoft Fabric Link
Problem:
When using Dataverse → Microsoft Fabric Link, there is currently no native monitoring, logging, or alerting capability in Dataverse to detect link failures or synchronization issues. Failures (such as shortcut creation errors, missing metadata tables, or incompl...
When using Dataverse → Microsoft Fabric Link, a single Dataverse table with an unsupported configuration (for example, a logical name exceeding Fabric shortcut limits) can cause shortcut creation to fail. This prevents Fabric from generating critical metadata tables (OptionsetMetadata, StateMetadata, StatusMetadata, TargetMetadata), even when all other tables are valid. This commonly occurs with Microsoft‑generated system tables (for example, Event Management / Marketing tables) and is not caused by customer misconfiguration. Suggested improvement: Skip or isolate unsupported tables instead of failing the entire link. Continue generating metadata tables for supported entities. Surface clear, actionable diagnostics identifying the specific table causing the failure. This would improve reliability, reduce analytics outages, and significantly lower escalation volume for enterprise customers.
Problem:
When using Dataverse → Microsoft Fabric Link, there is currently no native monitoring, logging, or alerting capability in Dataverse to detect link failures or synchronization issues. Failures (such as shortcut creation errors, missing metadata tables, or incompl...
Dataverse to Microsoft Fabric Link should gracefully handle unsupported tables instead of blocking metadata generation
When using Dataverse → Microsoft Fabric Link, a single Dataverse table with an unsupported configuration (for example, a logical name exceeding Fabric shortcut limits) can cause shortcut creation to fail. This prevents Fabric from generating critical metadata tables (OptionsetMetadata, StateMe...
CSV file generation needs to have column headers in Azure Synapse
The csv files generated do not have column headers, it only has data which is synced at the moment. This conclusion is confirmed by PG team. We need the function to generate the column headers instead of data sync only.