Power BI Button Trigger in Power Automate Returns Empty Body

Question

Power BI Button Trigger in Power Automate Returns Empty Body

Ash 25

Hi everyone,

I'm using the built-in Power Automate integration in Power BI to trigger a flow. I’ve configured the button and selected the data fields I want to pass into the flow. However, when I run the flow and inspect the trigger output, the body is completely empty.

Here’s what I’ve done so far:

Added the Power Automate visual in Power BI and selected the fields I want to send.
Created and edited the flow using the “On Power BI button clicked” trigger.
Inside the flow, I reference the expected data using @triggerOutputs()?['body']?['PPower Values'] in an Apply to each loop.

But the flow fails with this error:

The execution of template action 'Apply_to_each_2' failed: The result of the evaluation of 'foreach' expression '@triggerOutputs()?['body']?['PPower Values']' is of type 'Null'. The result must be a valid array.

I’ve confirmed that the trigger output body is empty, which seems to be the root cause.

Has anyone experienced this before? How can I ensure the data from Power BI is actually passed into the flow?

Thanks in advance!

0 comments

Answer accepted by question author

AceRobertT 14,455

Hello Ash. This issue arises most often due to the fact that the flow was created outside of the Power BI report context, or that the Power Automate visual is not correctly configured to pass in the data. The “On Power BI button clicked” trigger is only able to pass the data, if the flow was created through the Power BI visual, and the exact fields are added to the field well of the visual. If the flow was made in Power Automate independently and than linked, the flow does not know how to access report context data, and will result in an empty body.

To correct this, simply remake the flow by clicking the Power Automate button inside Power BI and selecting "Create new flow". This way, your flow is now bound to the report's data model. Also, double check that the fields you want to pass are assigned to the Power Automate visual's field well, and they are not blank in the current filter context. Do not use calculated columns or measures that could produce blank. If you are using @triggerOutputs()?['body']?['PPower Values'] , check that "PPower Values" is the exact name of the field as it appears in the visual.

Here's the reference: Power BI Data is empty in Power automate

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Best regards,

Ash 25 Reputation points

2025-07-30T14:54:43.76+00:00

Thank you for the reply, yes I am making all the flows from the Power BI app, in the report. And I have tried re-creating new flow. I am providing a screenshot from my trail project. As you can see the data are being selected to pass, and I could put that when applying to flow and compile. But when I run it I see this error and see the body being empty
Ash 25 Reputation points

2025-07-31T15:14:26.22+00:00

Very much apricate your reply, I want to update you that I have solved the issue in a wired way: https://community.fabric.microsoft.com/t5/Desktop/Power-Automate-in-Power-BI-error-quot-from-property-is-of-type/m-p/4262776

so after I published it, and view it from the power automate web backend, then the data is actually passed through. Also I need to concatenate and compose the data to pass it, I honestly have no idea why this works, but at least now it works
Sergi Martínez 0 Reputation points

2026-08-13T14:12:34.2833333+00:00

I am facing the same problem than in this case but I checked everything in the answer. I am still finding my trigger emplty when I run the flow... Is there any other thing that I should check that isn't said here?

Thanks!

1 additional answer

Your answer

Ash 25 Reputation points

2025-07-30T14:54:43.76+00:00

Thank you for the reply, yes I am making all the flows from the Power BI app, in the report. And I have tried re-creating new flow. I am providing a screenshot from my trail project. As you can see the data are being selected to pass, and I could put that when applying to flow and compile. But when I run it I see this error and see the body being empty
Ash 25 Reputation points

2025-07-31T15:14:26.22+00:00

Very much apricate your reply, I want to update you that I have solved the issue in a wired way: https://community.fabric.microsoft.com/t5/Desktop/Power-Automate-in-Power-BI-error-quot-from-property-is-of-type/m-p/4262776

so after I published it, and view it from the power automate web backend, then the data is actually passed through. Also I need to concatenate and compose the data to pass it, I honestly have no idea why this works, but at least now it works
Sergi Martínez 0 Reputation points

2026-08-13T14:12:34.2833333+00:00

I am facing the same problem than in this case but I checked everything in the answer. I am still finding my trigger emplty when I run the flow... Is there any other thing that I should check that isn't said here?

Thanks!

Answer 1

Hello Ash. Thanks for getting back. As you have already confirmed the flows were generated directly in Power BI and the fields are appropriately set within the visual, the best course of action is to very carefully verify the flow's trigger bindings and data context. At times, the Power BI visual only passes data when it is being rendered and not filtered out by slicers or page level filters. So, first make sure the data fields being passed are indeed populated in the current view where the button click occurs. Then within Power Automate, add a Compose action directly after the trigger and use the expression @triggerOutputs()?['body'] as this will give you a direct view of what is being received. If the output is still null try reducing the visual's fields down to just a single basic column, from your dataset, that you know has values. Sometimes more complex types, or calculated columns, fail to serialize with no warning. Also double check the field name you are referencing (when calling the value inside expression statements like ['PPower Values']); even a subtle naming or structure difference can result in null evaluation of the field identified. Once you are satisfied with the payload structure, you can then recreate your "Apply to each" logic. The approach described here provides a clean isolation to your problem and ensures any subsequent flow logic you build, is based around actual runtime data, not assumptions made from compile time configuration.