Forum Discussion
Blank data output when exporting via Power Automate Visual
Hi MOVC
Thank you for reaching out to the Microsoft Fabric community forum.This issue is related to trigger-binding (schema), not data, filters, or DAX. While the Table visual displays data correctly, the Power Automate visual does not access live query results. Instead, it uses a schema created at design time between Power BI and the flow.
In a working case, the flow’s trigger schema contains a rows array, which is how Power BI sends selected fields to Power Automate. In the failing case, the trigger schema is empty ("properties": {}), so the trigger does not recognize any fields. As a result, when the flow runs, it cannot deserialize the data and always returns "body": { "entity": {} }. This outcome is consistent without the schema, the output remains empty, regardless of the report data.
The problem occurs when the flow is created or edited without fields bound to the Power Automate visual, or if the binding is broken later. The schema is only generated when the trigger is first bound and does not update automatically if fields are added or changed afterward.
To resolve this, rebuild the trigger binding in Power BI. Open the report in Edit mode, select the Power Automate visual, and add all necessary fields. Then, click Edit to open the flow, delete and re-add the “On Power BI button clicked” trigger in the same session, save the flow, return to Power BI, and click Apply. This will regenerate and attach the correct schema to the flow.
Here are some references:
Power Automate button in Power BI suddenly returns empty entity {}
Create a Power Automate visual for Power BI - Power BI | Microsoft Learn
If you have any further questions, feel free to reach out and we'll be glad to assist.Regards,
Microsoft Fabric Community Support Team.
Power Automate visual can't access measures - only base table columns.
Fix: Create disconnected table visuals with measures converted to columns:
New table → DAX: SELECTEDCOLUMNS(SUMMARIZE(Table, Table[ID]), "MeasureCol", [YourMeasure])
Power Automate visual → use MeasureCol field (not measure)
Thanks for the response. I was concerned about calculated columns/measures/anything DAX and removed those from one example (I was just testing to see if I could export my IDs) and it still didn't work. I think I might have figured this out though:
For the flow/export that is working, it has the following in the codeview
Hi MOVC
Thank you for reaching out to the Microsoft Fabric community forum.This issue is related to trigger-binding (schema), not data, filters, or DAX. While the Table visual displays data correctly, the Power Automate visual does not access live query results. Instead, it uses a schema created at design time between Power BI and the flow.
In a working case, the flow’s trigger schema contains a rows array, which is how Power BI sends selected fields to Power Automate. In the failing case, the trigger schema is empty ("properties": {}), so the trigger does not recognize any fields. As a result, when the flow runs, it cannot deserialize the data and always returns "body": { "entity": {} }. This outcome is consistent without the schema, the output remains empty, regardless of the report data.
The problem occurs when the flow is created or edited without fields bound to the Power Automate visual, or if the binding is broken later. The schema is only generated when the trigger is first bound and does not update automatically if fields are added or changed afterward.
To resolve this, rebuild the trigger binding in Power BI. Open the report in Edit mode, select the Power Automate visual, and add all necessary fields. Then, click Edit to open the flow, delete and re-add the “On Power BI button clicked” trigger in the same session, save the flow, return to Power BI, and click Apply. This will regenerate and attach the correct schema to the flow.
Here are some references:
Power Automate button in Power BI suddenly returns empty entity {}
Create a Power Automate visual for Power BI - Power BI | Microsoft Learn
If you have any further questions, feel free to reach out and we'll be glad to assist.Regards,
Microsoft Fabric Community Support Team.
Thanks. I figured the specific mistake I made was the second time around creating the visual and applying the workflow before adding data to the data field. I think it's unfortunate it behaves this way (if you want to add data into a static flow later you always have to delete and readd the visual?) but as long as we know how it works it's fine.