You’re offline. This is a read only version of the page.
15
Hi all,
two of my flows are suddenly failing since saturday, there have been no changes from my end. The action that exports a file from paginated report (PBI premium per user) throws the error "Effective identity on datasources with SSO enabled is not supported". The two flows affected are supposed to export the files to a SFTP server in the following step.
All other flows exporting paginated reports from the same instance work perfectly fine. The only difference in setup is that the following action is Send to user per Mail instead of Create file on SFTP.
The error message implies that there might be an issue with my PBI connection, but many flows using the same connection work well. I have also set up a simple flow only with the export action. The two reports in question won't work (error hits immediately), all others will.
Any ideas?
Here's detailed error info:
Many thanks in advance,
Kathrin
Yes, Re-redeployment is mandatory, it didn't work otherwise for me even after updating connections.
Republishing did not work for me. I went to the paginated report in the service, hovered over the title, clicked the three dots on the right and selected Manage. Once I clicked Manage, I could then click Edit credentials and re-enter them and then it finally worked again.
I have reports using Power BI dataset as the datasource and failed too. It looks like recreating the report and publish is the only solution.
Our paginated report dataset is connecting to Power BI premium (XMLA). Today we also encountered this problem. Re-entering credentials did not work. After hours searching the issue we tried to change the connection type.
It seemed we were using in the past year a connection type Analysis Services, which has worked perfectly until this week. We fixed it in de rdl-file:
- change to type "Power BI Dataset"
- Build/choose the right dataset
- Re-enter credentials
- publish it to power bi
Where did you find this? I am looking in the workspace where my paginated reports are located, but don't see this. My reports are connected to an AAS model. (Never mind, I found it. It's under Manage of the three dot menu on the report.)
Reentering credentials works for AAS as the datasource but it does not work if the datasource is a Power BI dataset. I tried to republish my reports and it does not work either.
The problem seems to be fixed, All I did was reentering the credentials on the Power BI Service.
We got hit by this one today out of the blue also; following some of the advice above from @j500sut, I took over the dataset in the service and re-entered the credentials (OAuth - O365) which appears to have done the trick. My reports are all pointing to an AAS instance.
The concerns here however are:
- Will this work again tomorrow, or the day after etc
- Do we need to apply this on all reports that are currently being picked up by PowerAutomate
- If not, what are the exceptions?
- When will a 'fix' be applied!
#1
WarrenBelz
146,653
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
65,999
Most Valuable Professional
Share
Report
All responses (
Answers (
