Power BI Power Automate Visual – Data Not Passed to Flow Trigger

(3) Share

Report

Posted on by CG-22071529-0

I am unable to get any data from the Power BI Power Automate visual into a triggered Power Automate flow—no matter what configuration I use. This is severely blocking our reporting automation, and I have exhausted all recommended and advanced troubleshooting steps.

Symptoms:

The flow trigger (“On Power BI button clicked”) always receives either a completely empty payload ({}) or an empty array ("rows": []).
No dynamic content (fields, measures, columns) is ever available in the Compose or any step after the trigger.
This happens for both brand new and existing PBIX files, in new and existing workspaces, with new and existing flows, using different browsers, and even after publishing to the Power BI Service

Troubleshooting steps I have tried (all failed):

Created new PBIX files with a single table and a simple DAX measure (Test Measure = "Hello World")
Added only measures (not columns or calculated columns) to the Power Automate visual’s Fields well
Tried using columns from a data table (with and without filters).
Ensured all fields return non-blank values in a Table visual for the same filter context.
Started flows strictly from the Power BI visual (“Create new flow”), never from the Power Automate designer directly.
Rebuilt the visual, flow, and workspace multiple times.
Tested in Power BI Desktop and Power BI Service (browser, incognito, and different accounts).
Confirmed no Row-Level Security or permissions issues are blocking data.
Used both summary string measures and table arrays.
Monitored and followed recent community posts about the same issue (see below).

Additional details:

The flow trigger always includes splitOn: "@triggerBody()['rows']", and the schema is either blank or always expects an array.
No field, measure, or column (even if visible in a Table visual) is ever passed to the flow.
The issue persists even with the most basic scenario: one measure, one row, new everything.
I have confirmed multiple other users are experiencing this bug, including recent posts on the Microsoft Community:
- Power BI data not flowing to Power Automate on Power BI button: https://community.fabric.microsoft.com/t5/Desktop/Power-BI-data-not-flowing-to-Power-Automate-on-Power-BI-button/m-p/4607751#M138067

Categories:

General topics

I have the same question (1)

All responses (3)

Answers (0)

Suggested answer

Jon Unzueta 1,827 Super User 2025 Season 2 on at

Like (0)

Report
@CG-22071529-0

Based on the latest community discussions and confirmed reports, you are not alone—this is a widespread and currently unresolved issue affecting the Power BI Power Automate visual, where no data is passed to the flow trigger, even in the simplest configurations.

🔍 Key Findings from the Community

Confirmed Bug (July 2025)
Multiple users have reported that the “On Power BI button clicked” trigger receives an empty payload ({}) or an empty rows array, regardless of the data passed in the visual.

No Reliable Workaround Yet
Users have tried:

Creating flows from within the Power BI visual (not from Power Automate directly)

Using only measures or only columns

Rebuilding PBIX files, visuals, and flows

Testing in different browsers and environments
...all with no success.

Possible Cause: Designer Mode Conflict
One user resolved a similar issue by deleting the trigger and re-adding it from within the Power BI visual, not from Power Automate directly . This suggests a conflict between the new and old designer modes in Power Automate.

Known Limitations (from Microsoft docs and community):

Flows must be created within the Power BI visual, not in Power Automate directly.

The Power Automate visual only works in the default environment.

Manual inputs to the button are not supported.

Embedded reports (e.g., in SharePoint) may not trigger flows properly
3
.

✅ Recommended Actions

Here’s what you can try next:

1. Recreate the Flow from the Visual

Delete the existing flow.

In Power BI, click the Power Automate visual → “Create new flow”.

Add a simple Compose action to inspect the payload.

Publish and test again.

2. Avoid Editing in Power Automate Designer

Do not open or edit the flow in Power Automate directly.

Only use the Power BI visual interface to configure the flow.

3. Check Environment

Ensure the flow is created in your default environment.

Avoid using custom environments or solutions.

4. Report the Bug

Since this appears to be a regression or platform-level issue, I recommend:

Submitting a support ticket via your Microsoft 365 admin portal.

Referencing this community thread .

🏷️ Tag me if you have any further questions or if the issue persists.

✅ Click "Accept as Solution" if my post helped resolve your issue—it helps others facing similar problems.

❤️ Give it a Like if you found the approach useful in any way.

Was this reply helpful? Yes No
lbendlin 8,479 Super User 2025 Season 2 on at

Like (0)

Report

The workaround of removing and re-adding the trigger from within the Power BI visual edit dialog is no longer working fo me.

It is worth noting that the issue seems to affect only visuals/flows that have been created or modified recently. Older, "untouched" button/flow combinations continue to work.

When I last raised a ticket about this the Power BI and Power Platform support teams pointed fingers at each other and were unwilling to engage in a meaningful conversation or root cause investigation. Maybe this time it will be different?

Was this reply helpful? Yes No
JanRak 10 on at

Like (0)

Report

Hi
A colleague found a workaround. Maybe it will be useful for someone.

1. Create a flow within PowerBI (not sure if she used the desktop PowerBI or the online version). Use a template "Send a Teams message from Power BI"
You can see in the screen below that the PowerBI data is available via Dynamic content! Potentially, you might need to add that content to the Teams message.

2. And the funny thing is: don't remove that "Post message in a chat or channel" action, as that will cause the flow to lose access to the Power BI data!!! Maybe some other templates created within Power BI will do the trick as well. I haven't tested it.

Was this reply helpful? Yes No