Forum Discussion
Power BI API Call feasibility
Can below scenarios be possible in Power BI?
Scenario1:
1. User will input values in a form using a dropdown/filters/slicers, example Account ID and Product ID ( This form needs to be created in Power BI)
2. User will click on Submit Button ( This button needs to be created in Power BI)
3. An API call will trigger after button click which will fetch Power BI filter or slicers values selected in Step1 from database using Python or Java code
Scenario2:
1. User will input values in a form using a dropdown/filters/slicers, example Account ID and Product ID ( This form needs to be created in Power BI)
2. User will click on Submit Button ( This button needs to be created in Power BI)
3. A Power Automate Flow will trigger after button click which will fetch Power BI filter or slicers values selected in Step1 from database
Go with Scenario 2 - Power Automate Route
Why this works better:
- Power BI doesn't have true submit buttons, but Power Automate can bridge this gap
- Microsoft's native integration means fewer compatibility issues
- More reliable than trying to force Python/Java calls from Power BI
Implementation Steps:
Step 1: Power BI Setup
- Create your report with slicers for Account ID and Product ID
- Set up report parameters that capture slicer selections
- Configure the report to work with Power Automate triggers
Step 2: Power Automate Flow
- Create flow triggered by Power BI data changes or manual trigger
- Use "Get data from Power BI" action to fetch current filter values
- Add your database API call using HTTP connector
- Handle response and update target systems
Step 3: User Experience
- Users interact with normal Power BI slicers (feels like a form)
- Add a bookmark or button that triggers the flow
- Flow runs in background and processes the selected values
Fixed? ✓ Mark it • Share it • Help others!
Best Regards,
Jainesh Poojara | Power BI Developer
5 Replies
Hey powerbiexpert22,
Here's how to capture current slicer values in Power BI for Power Automate:
Quick Solution Steps
Power BI Side:
- Create report parameters matching your slicer fields (Account ID, Product ID)
- Link slicers to these parameters in slicer properties
- Publish report to Power BI Service
Power Automate Side:
- Create flow with "Power BI" trigger or manual trigger
- Add "Get dataset parameters" action from Power BI connector
- Use retrieved parameter values in your HTTP/API calls
User Experience:
- Add Power Automate visual to your report page
- Users select slicers → click flow button → values get processed
- Flow runs with current slicer selections automatically
Key Point: The "Get dataset parameters" action is what pulls your current slicer values. This works because parameters update when slicers change.
Fixed? ✓ Mark it • Share it • Help others!
Best Regards,
Jainesh Poojara | Power BI Developer
Hi powerbiexpert22 ,
Thank you jaineshp for the response provided!
Has your issue been resolved? If the response provided by the community member addressed your query, could you please confirm? It helps us ensure that the solutions provided are effective and beneficial for everyone.
Thank you for your understandingHi powerbiexpert22 ,
I wanted to follow up and see if you had a chance to review the information shared. If you have any further questions or need additional assistance, feel free to reach out.
Thank you.
Go with Scenario 2 - Power Automate Route
Why this works better:
- Power BI doesn't have true submit buttons, but Power Automate can bridge this gap
- Microsoft's native integration means fewer compatibility issues
- More reliable than trying to force Python/Java calls from Power BI
Implementation Steps:
Step 1: Power BI Setup
- Create your report with slicers for Account ID and Product ID
- Set up report parameters that capture slicer selections
- Configure the report to work with Power Automate triggers
Step 2: Power Automate Flow
- Create flow triggered by Power BI data changes or manual trigger
- Use "Get data from Power BI" action to fetch current filter values
- Add your database API call using HTTP connector
- Handle response and update target systems
Step 3: User Experience
- Users interact with normal Power BI slicers (feels like a form)
- Add a bookmark or button that triggers the flow
- Flow runs in background and processes the selected values
Fixed? ✓ Mark it • Share it • Help others!
Best Regards,
Jainesh Poojara | Power BI Developer
