Query Diagnostics enhancements
Important
This content is archived and is not being updated. For the latest documentation, see Microsoft Power Platform product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.
| Enabled for | Public preview | General availability |
|---|---|---|
| Admins, makers, or analysts, automatically |  Oct 14, 2019 |
Mar 30, 2020 |
Feature details
Another major area of investment going forward is in Query Diagnostics.
Often, customers connect to slow data sources and then create queries with many or complex transformation steps, resulting in slow queries. To debug issues with queries, customers need to look into Power Query traces to understand whether their queries are pushed to the data source (if the data source supports the transformations being used), or whether Power Query compensated and ran those queries locally within the Mashup Engine.
In a few months, a new user experience surface will be added to the Power Query editor, making it easier for customers to gain insights, including:
- Knowledge of what data source queries are being generated to run their M queries.
- Knowledge of what data source queries are being generated to retrieve schema and metadata information.
- The amount of time queries take to run within the data source versus locally in the Mashup Engine.
Query Diagnostics will allow customers to more easily troubleshoot issues with their queries and identify potential optimizations. In addition to all these smart data preparation capabilities that will result in customer-facing features, Power Query will also become smarter about understanding data transformation usage patterns based on telemetry (non-PII), so that these and future capabilities can be further refined.
See also
Power BI (blog)