Urgent: Dynamic API Calls in Power BI Slicers

[jesikamaurya]

1. Trigger API Call Dynamically on Slicer Selection:

   • The slicer contains numeric values (e.g., 100, 101, 102, etc.).

   • When a user selects a value, the API request should be updated dynamically.

   • Example API format:

     "https://api.freeapi.app/api/v1/public/randomjokes?limit=SlicerSelectedValue&query=science&inc=categories%252Cid%252Ccontent&page="

   • If the user selects 103, the API call should become:

     "https://api.freeapi.app/api/v1/public/randomjokes?limit=103&query=science&inc=categories%252Cid%252Ccontent&page="

   • The API should execute immediately after the selection.

2. Refresh Power BI Instantly After API Call:

   • Once the API request is made, Power BI should immediately refresh to update the visuals.

   • This ensures the latest data is retrieved and displayed dynamically.

3. Store API Response in a Table:

   • The response from the API needs to be captured and stored in a Power BI table.

   • This allows further data processing, analysis, or visualization based on the retrieved data.

4. Display API Response Data in a New Slicer:

   • After storing the API response, a new slicer should be created to display the relevant data from the response.

   • This slicer will be dynamically updated based on the API results.

Challenges & Required Assistance:

• How to dynamically trigger an API request based on slicer selection?

• How to refresh Power BI instantly after calling the API?

• How to store the API response in a table efficiently?

• How to link the API response data to another slicer in Power BI?
  

I am looking for guidance on the best approach to implement this workflow, preferably using Power Automate or other efficient methods. Any help or insights would be greatly appreciated!

[lbendlin]

This here is a forum where users help users, time permitting.  For urgent requests contact a Microsoft partner near you.

Power BI is (still, in 2025!!!) the wrong tool for that. Watch the Ignite videos that talk about custom data write back functions. So Microsoft seems to be thinking about this, but there is no timeline whatsoever.