Forum Discussion

MOVC's avatar
MOVC
Resolver I
2 months ago
Solved

Power Automate Visual sending empty data

I have a fairly standard report with a Power Automate visual. The flow sends a single record for processing for some other business activity. When I was setting this up recently it was all working as expected and when I published it live yesterday it was running as it should. Today however every flow run fails, because there is no data in the body of the trigger.

 

{
    "headers": {
        "Accept": "*/*",
......
    },
    "body": {
        "entity": {}
    }
}
 
Previously:
 
{
    "headers": {
        "Accept": "*/*",
...........
    },
    "body": {
        "entity": {
            "Power BI values": [
                {
                    "Delegation": "redacted",
......
                }
            ]
        }
 
I have tried creating a new PA visual but I get the same issue. If I pick a different flow from the menu then it works. Is it possible to "break" a flow somehow? I would rather not rebuild the whole flow from scratch and looking at other posts it seems that might not help. Does anyone have any ideas how to resolve this?
Need Help
  • Shai_Karmani's avatar
    Shai_Karmani
    2 months ago

    Hey

    Known MS bug :
    https://community.fabric.microsoft.com/t5/Desktop/Power-BI-data-not-flowing-to-Power-Automate-on-Power-BI-button/m-p/3824990


    not something you broke. It's a conflict between the new and old Power Automate designer modes. If the flow ever gets saved via the new designer (happens silently when you open it from make.powerautomate.com instead of via the PBI visual), the trigger gets corrupted and body.entity comes through empty. That's why rebuilding doesn't help , the new flow gets bitten by the same bug.

    Fix without rebuilding:

    1. Open the flow from inside the Power BI Power Automate visual (Edit on the visual and then Edit flow). Not from Power Automate directly.
    2. Delete the "On Power BI button clicked" trigger.
    3. Re-add it from the visual editor and re-bind your fields.
    4. Save and make the last action before saving be re-selecting the data/array field. Anything edited after that re-selection re-corrupts it.
    5. Test via Ctrl+Click on the button in the report (the "Run" inside the designer always sends an empty body  don't trust it).

    Going forward: only ever edit the flow through the PBI visual, never from Power Automate directly. That keeps it pinned to the old designer.

    If this helped, a thumbs up and accepting the solution would be appreciated.

     

    Best,
    Shai Karmani

    Let's connect in LinkedIn



2 Replies

  • Shai_Karmani's avatar
    Shai_Karmani
    Super User
    2 months ago

    Hey

    Known MS bug :
    https://community.fabric.microsoft.com/t5/Desktop/Power-BI-data-not-flowing-to-Power-Automate-on-Power-BI-button/m-p/3824990


    not something you broke. It's a conflict between the new and old Power Automate designer modes. If the flow ever gets saved via the new designer (happens silently when you open it from make.powerautomate.com instead of via the PBI visual), the trigger gets corrupted and body.entity comes through empty. That's why rebuilding doesn't help , the new flow gets bitten by the same bug.

    Fix without rebuilding:

    1. Open the flow from inside the Power BI Power Automate visual (Edit on the visual and then Edit flow). Not from Power Automate directly.
    2. Delete the "On Power BI button clicked" trigger.
    3. Re-add it from the visual editor and re-bind your fields.
    4. Save and make the last action before saving be re-selecting the data/array field. Anything edited after that re-selection re-corrupts it.
    5. Test via Ctrl+Click on the button in the report (the "Run" inside the designer always sends an empty body  don't trust it).

    Going forward: only ever edit the flow through the PBI visual, never from Power Automate directly. That keeps it pinned to the old designer.

    If this helped, a thumbs up and accepting the solution would be appreciated.

     

    Best,
    Shai Karmani

    Let's connect in LinkedIn



    • MOVC's avatar
      MOVC
      Resolver I
      2 months ago

      Thanks, this fixed it.

       

      I've had a bunch of issues with PA in PBI in the past it clearly has issues...