Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
The Export File Option for Paginated Reports in Power Automate started failing today with the above error, after running successfully for months. The report works fine when executed directly.
Hi,
I would suggest opening the RDL report in report builder and remove datasources which aren't in use. In particular if you have datasources of type PBIDATASET in your RDL report, and they reference a dataset which doesn't exist anymore, then this issue might happen.
Modifying the RDL report can also be done in a text editor, for example if you have in your .rdl file the following:
<DataSources>
<DataSource Name="Datasource_for_test">
<rd:SecurityType>None</rd:SecurityType>
<ConnectionProperties>
<DataProvider>PBIDATASET</DataProvider>
<ConnectString>Data Source=pbiazure://api.powerbi.com/;Identity Provider="https://login.microsoftonline.com/common, https://analysis.windows.net/powerbi/api, <some_guid>";Initial Catalog=sobe_wowvirtualserver-<some_guid>;Integrated Security=ClaimsToken</ConnectString>
</ConnectionProperties>
<rd:DataSourceID><some_guid></rd:DataSourceID>
<rd:PowerBIWorkspaceName>SomeWS</rd:PowerBIWorkspaceName>
<rd:PowerBIDatasetName>For_test</rd:PowerBIDatasetName>
</DataSource>
<DataSource Name="Datasource_PROD">
<rd:SecurityType>None</rd:SecurityType>
<ConnectionProperties>
<DataProvider>PBIDATASET</DataProvider>
<ConnectString>Data Source=pbiazure://api.powerbi.com/;Identity Provider="https://login.microsoftonline.com/common, https://analysis.windows.net/powerbi/api, <some_guid>";Initial Catalog=sobe_wowvirtualserver-<some_guid>;Integrated Security=ClaimsToken</ConnectString>
</ConnectionProperties>
<rd:DataSourceID><some_guid></rd:DataSourceID>
<rd:PowerBIWorkspaceName>SomeWS</rd:PowerBIWorkspaceName>
<rd:PowerBIDatasetName>PROD</rd:PowerBIDatasetName>
</DataSource>
</DataSources>
Then your report has 2 datasources of PBIDATASET. You can look for each of the datasource name in the rest of the .rdl file, and if it's not referenced anywhere then it should be removed.
Hi, @asocorrocognex
Have submited this issue internal to confirm(ICM: 285887312), would update here as soon as possible if there is any update about it.
Best Regards,
Community Support Team _Charlotte
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
I am seeing this issue as well with my flows using export to paginated report. Wondering if it has anything to do with the issue reported on Microsoft
Power BI customers embedding "Published To Web" reports into a website using the HTML generated, may experience intermittent issues loading visuals. Engineers are working on a fix and expect it to be deployed to all regions by end-of-day 03/12/2022
As a workaround, customers can append "&angularOnlyReportEmbed=false" at the end of src URL in the html code generated in Power BI
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.