Description: Power BI to support is needed for dynamic API calls triggered by slicer selections when using DirectQuery mode. Use Case: In my report, I use a slicer to select an ID. Ideally, each time a user selects a new ID, Power BI should trigger a fresh API call (e.g., via Web.Contents or a custom connector), using the selected ID as a parameter, and update the visuals accordingly. This would enable just-in-time data retrieval, improving performance and responsiveness—especially when dealing with large or external datasets accessible only via REST APIs. Most importantly, this approach removes the need to pre-load and store the entire dataset before querying it. Current Limitation: Power BI currently does not support this functionality in DirectQuery mode. While dynamic M parameters are available for some data sources like SQL Server or SAP, they are not supported for REST APIs via "web.contents". Although some workarounds proposed by some users, they introduce significant complexity, additional system layers like power apps or power automate, and lack seamless integration and real-time interactivity. Suggested Enhancements: Extend support for dynamic M parameters to REST API and "web.contents" sources in DirectQuery. Enable slicer values to bind to query parameters for triggering API calls. Provide a refresh mechanism that allows real-time API data retrieval based on user interaction. Impact: This capability would be a game-changer for integrating external systems—especially those accessible only via API—into Power BI without the overhead of duplicating data into intermediary storage. It would support more scalable, responsive, and user-driven reporting experiences.
... View more