Flow Failing at Export To File for Paginated Reports

[vanilk]

Hi @CST ,

All our flows are failing from this morning at this  Export To File for Paginated Reports  step. Are there any changes Microsoft rolled since yesterday night ?  Everything was working until last night. The error message return is added below for your reference.  Can someone please check and update what needs to be done?

"body": {
"error": {
"code": "InvalidRequest",
"message": "Only an admin of every workspace containing a dataset used in this report can export paginated reports with an effective identity"
}
}
}

Thanks,

Anil Kumar

[Anonymous]

I just had a word with Microsoft Support team. They rolled out an update which caused this issue. According to the technician 281 clients of Microsoft are affected so far. The backend team is aware of this issue and working on rolling the update back to fix this issue.

[BriceB]

I discovered the same issue today 1st of Feb 2022- Can we please have any feedback from Microsoft?

[ac330u]

The backend team from Microsoft is going to fix this issue for all 281 clients or the backend team from your company only?

[meeshmeesh]

Having this issue as well.

[rjhale]

I only started seeing this problem as of this morning.  I had several processes run as expected last night (1/31/2022) that use this functionality, and the account associated with the Power BI action was only a Contributor of the workspace.  I gave that account Admin access after seeing the error this morning, and that fixed the problem.  Obviously, we don't want this account to retain Admin access to the workspace, so it would be nice to know what Microsoft is doing to resolve the permissions issue.  

Thank you. 

[ac330u]

Just got off the phone with Microsoft (had to open a ticket directly).. It appears that this was impacted after their recent update for that particular connector (per the below 1/27/2022 article). Apparently in the new update, it is not allowed to use "Power BI" as a Dataset.. Which is clearly a mistake as Paginated Reports "IS" part of Power BI and in fact the first "Recommended" Dataset when building a paginated report inside of Report Builder, hence the reason it seems to be generating a BadGateway error 502. I recorded all network and console activity (browser trace) while replicating the issue and sent all of our flow information. They are going to attempt to roll back part of the update relating to Power BI as a dataset (fingers crossed).

https://docs.microsoft.com/en-us/power-bi/developer/embedded/export-paginated-report#considerations-...

[Futumpch1]

Same issue here 503 gateway error when using flow to generate a paginated report on the power bi service. Data set is in a non premium area.

Paginated report runs fine in the power bi service. 

[Anonymous]

For all affected clients.

[Anonymous]

I have the same trouble. We changed permission to admin but we have still had same "Only an admin of every workspace containing a dataset used in this report can export paginated reports with an effective identity" exception. Microsoft PowerBI team, please help about this issue!

[JulianaD]

Successful workaround: 

1) Add the dataset owner to your flow as a flow owner.

2) Use their connection: Have the dataset owner edit the flow, in all cards/actions for 'Export file for paginated report', click on the ellipses, add new connection (add their connection, set it to their connection), save. 

I had 3 scheduled flows fail on Feb 1, all on card 'Export file for paginated report', with error message 'Only an admin of every workspace containing a dataset used in this report can export paginated reports with an effective identity'. I did the above steps and then they all ran successfully.
Though, I suppose this would only work if you are using one dataset or if the owner is the same for all the datasets. 

Cheers, 

Juliana Donkersgoed

[Anonymous]

In my case I am the owner of the dataset and flow is created by me too. Also, connections are made using my credentials. Flow still fails, unfortunately.

[Futumpch1]

Yes I have just tried thia and failed :(.

Have a teams meeting with customer support later lets see what happens.

[Futumpch1]

fix is rollying out today (NA) and EU tomorrow.

Fingers crossed

[venkkateshg99]

Great News. Please let us know if this issue resolves for you.

[Anonymous]

Our flow is working today. Thanks everyone!

[zeppzach]

Our flows started working this morning as well. 

[ac330u]

Our flows started working again 🙂 

[SchafeCa]

Hi we are in Australia having same issue is there  an update when the expected rollout for this region may occur hoping this will resolve our issues 🙂

[Anonymous]

For Australia Region, flows are still not working. So, I am guessing the rollback has not taken place yet. I will try and get in touch with Microsoft Technician today and find out more on this.

[AmirGh]

It is working for Australia as well (for me)