🐞 Bug Report + 🔧 Feature Request: Power BI Desktop (August 2025 Release)
Title: Native SQL Parameter Binding Broken + Dynamic Parameterization Still Unsupported
Product: Power BI Desktop
Version: August 2025
Mode: Import and DirectQuery
Data Source: SQL Server (AdventureWorks2022)
🐞 Bug Summary
Since updating to the August 2025 release, Power BI Desktop fails to bind parameters in native SQL queries using , even when syntax is correct and parameters are wrapped in records.
Symptoms:
- Error:
- Occurs even with hardcoded values and correct record structure.
- Parameter binding worked in earlier versions using identical syntax.
Impact:
- Breaks previously working workflows.
- Forces users to abandon parameterization and fall back on string interpolation.
- Undermines security and query folding in DirectQuery mode.
🔧 Feature Request
Request: Enable full dynamic parameterization in Power BI Desktop, including:
- Slicer-to-Parameter Binding for native SQL queries.
- Support for parameterized SQL expressions like ISNULL() in DirectQuery.
- Automatic sync between slicer visuals and Power Query parameters.
- Restore and document proper behavior of Value.NativeQuery with ADO.NET parameters.
Use Case:
Building dynamic, slicer-driven reports using AdventureWorks2022 data, where PurchaseOrderID is selected via a slicer and passed into a native SQL query. Current workaround requires manual parameter updates and string injection, which is fragile and not scalable.
🧠 Suggested Fixes
- Patch Value.NativeQuery to correctly bind parameters again.
- Expand dynamic M query parameter support to native SQL.
- Allow ISNULL() and similar expressions in DirectQuery mode.
- Provide UI-level sync between slicers and Power Query parameters.
