Power Automate Trigger in Power BI

(0) Share

Report

Posted on by MA-11061403-0

I’m currently facing an issue with the Power Automate integration from Power BI.

Previously, the flow was working as expected, and the Power Automate button in Power BI was successfully passing selected values to Power Automate. However, it has suddenly stopped working.

Now, when I trigger the Power Automate button from Power BI, the flow runs but does not receive any values — the input data appears to be empty.

Could you please help investigate what might have caused this issue and advise on how to resolve it?

Thanks in advance for your support.

Best regards,

Mufid

Categories:

Connector development

Using connectors

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Assisted by AI

sannavajjala87 304 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hi,
The screenshot tells the story: your trigger fires fine (0s, green check), but the body comes back as "entity": {}, so Power BI is sending an empty payload. Your flow is fine, the data just isn't coming across from the Power BI side.
The most common cause right now is the new Power Automate designer. If the flow got opened or edited in the new designer (directly in Power Automate instead of through the Power BI visual), it's a known issue that breaks the trigger's link to the report data and you start getting an empty entity. A platform update can also push flows into the new designer on its own, which would explain why it stopped with no changes on your end.
The reliable fix is to rebind the flow through the Power BI visual, not by editing it in Power Automate:

In the report (edit mode), select the Power Automate visual and use its Edit option, or choose Create new flow from the visual and rebuild it there. Creating or editing from inside the visual is what reconnects the trigger to the report's data model.

While you're there, confirm your fields are still in the visual's Fields well (if it's blank, nothing gets sent), and that they aren't empty under your current filter or slicer selection.

Republish and test.

This is a known, fairly widespread issue, so you're not doing anything wrong. Rebuilding from the visual and avoiding the new designer afterward is what fixes it.

Was this reply helpful? Yes No
Suggested answer

MA-11061403-0 2 on at

Like (0)

Report
Copy link

Link copied!

Thanks for the response, now it's working, I turned it to the new design, and the Array trigger was not selected, so I just selected and it's triggering now:

Was this reply helpful? Yes No