Power BI data not flowing to Power Automate 'on Power BI button clicked'

[bdsimpsn_]

I have two similar flows triggered when clicking a button on my power BI report.

One works perfectly, getting the data from the table rows. However the second one I have made, which uses similar data from a different table, is not being transferred across to the power automate flow and the schema and entity are empty.

I've attempted the following:

- Refreshing the dataset

- Creating a new flow and applying it to the button

- Having the table and button on a separate page

Does anyone know why and how to fix this?

 

Onboarding flow - working

Onboarding data - working

Offboarding flow - not working

 

Offboarding data - not working

[Sjoshy]

This has nothing to do with filters or anything like that. I had a similar issue this week. All of a sudden my Power BI data wasn't send anymore. I compared the run history (csv) and noticed that the trigger step had changed while I didn't make any changes to it.

After doing a little digging I found the root cause:
It looks like this is a bug in the way the "new designer" mode and the old designer mode of a flow interact (save your flow). You probably started the creation of the flow from within Power BI (old mode).  If you (accidentally) open the flow in Power Automate in the "new designer" mode it looks like some settings are modified.

If you look at the first step/trigger (in the "new designer" mode) you will notice that the "Array" has gone blank even though you haven't made changes:

Change this value back to:

Save your flow and it will send data again from PowerBi.

[dmc1977 · Accepted solution]

This was what caused the issue in my case also, opening in the new desinger mode direct in Power Automate rather than via the Power BI Power Automate Visual edit. 

I didn't have the specific settings issue with the blank Array field however deleting the On Power BI button trigger and re-adding it via the Power BI visual edit resolved the issue for me whilst doing same from within the flow in Power Apps or Power Automate directly did not. 

[lbendlin]

 deleting the On Power BI button trigger and re-adding it via the Power BI visual edit resolved the issue

confirmed workaround. Thank you!

[tianshen65]

same issue here, is it a MSFT bug?

[Sjoshy]

I had a similar issue this week. All of a sudden my Power BI data wasn't send anymore. I compared the run history (csv) and noticed that the trigger step had changed while I didn't make any changes to it.

After doing a little digging I found the root cause:
It looks like this is a bug in the way the "new designer" mode and the old designer mode of a flow interact (save your flow). You probably started the creation of the flow from within Power BI (old mode).  If you (accidentally) open the flow in Power Automate in the "new designer" mode it looks like some settings are modified.

If you look at the first step/trigger (in the "new designer" mode) you will notice that the "Array" has gone blank even though you haven't made changes:

Change this value back to:

Save your flow and it will send data again from PowerBi.

[PVO3]

Thank you for this awnser!

What a buggy mess this is. In needed to switch multiple times between old and new design to even see this 'Split on' option and be able to save the adjusted Array. It finally did the job after a couple of hours.

[gianpaixao]

I have the same issue. Funny thing that my flow worked well several days ago. Today, the same flow that worked before started to return "{}" in the output.

[lbendlin]

The Power Automate button gets its data from the specified columns (in a cross join if needed) BUT impacted by the applied filters. Check the filters. 

The easiest way is to use a table visual without totals, then make sure it renders the expected data, and then convert it to a Flow Button visual.

[bdsimpsn_]

Hi @lbendlin 

Thanks for your response. There's no filters set on this page at all and the table has the data I'm expecting.

Visual table A is pulling data from a separate table than visual table B, and the flow running for visual table A is working perfectly so I'm not understanding why the flow running for visual table B isn't.

[lbendlin]

the table visuals are not important,  the filter context of the flow visual is the deciding element.