Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
So - little bit of an odd one here. Posted in PowerBI as the issue is with Paginated Reports, however I am using a lot of the Power Platform.
If I have posted this in the wrong place - just let me know and i'll post in the correct board!!
I have build a solution in Power Apps that collects some information, within the App I have a Form which writes to Sharepoint Lists.
All of this is working as intended and all data in the SPO List is correct and intact.
On submission of the PowerApp I call a Power Automate Flow which picks up some variables from the PowerApp and triggers a Power BI connector to 'Export to File from Paginated Reports'.
This (within the flow) then emails the report to the user that requested it from the PowerApp.
All of this works as intended.
The paginated report is a quite complex thing - where a single report is run, but contined within there are a number of subreports, these run or hide based on the parameters sent by the PowerApp - but essentially pulls the data from the SPO List and is triggered based on SPO ID.
When the paginated report is run manually - this works as intended 100% of the time.
When each subreport is run manually - this works as intended 100% of the time.
When you run the process end to end (PowerApp to Recieving Email via Power Automate) some fields go missing in the Paginated Report.
This is what happens when its not rendering as it should: (data obscured for security reasons...)
No Total field passes through - and therefore SUBTOTAL = 0 as its summing 0.
Also Support line hides as this is a hidden expression based on that figure in the SPO dataset.
This is how it should appear: (again fake data inserted for security reasons)
I cant figure out why it work work manually - but as soon as you trigger it through Power Automate fields would go blank?
When I inspect the Dataset - all data inside the Paginated Report is there and visible. It just doesn't show when run though Powr Automate. It does on Run and when published and run.
So to recap:
Does anyone have any thoughts?
Thanks
Dan
Solved! Go to Solution.
Closing the loop as I have resolved this!
Firstly - everything I tried came up with the same result:
Data Source was PowerQuery to a SharePoint List.
As stated in the initial issue / question, when run independently the data all shows and displays as expected. It's only when run through a Power Automate Flow that the data doesn't appear.
So the fix...
The only thing that worked was to change the data source from PowerQuery to a Power BI Semantic Model.
This has a number of further limitations as the flow then needs to refresh the dataset (which is pointed at the SPO List) before it processess the Paginated Report - but it has resolved the issue.
Not ideal - but its working.
Hope this helps anyone else that has a similar issue moving forward!
Thanks
Dan
Thanks @v-yohua-msft,
All parameters are correctly passed (there is just the one - the SharePoint List ID).
I have verified the SharePoint list data is in-tact - this issue is consistant with resubmits of older submissions as well as new ones - consistantly not showing the same fields.
Subreports are properly linked and satify their data dependencies.
The only thing is it does take over two minutes to run - but the flow is set to be asyncronous.
It does feel like it could be a latency issue, but the consistant way it fails is making me question if its a bug?!
Thanks
Dan
Closing the loop as I have resolved this!
Firstly - everything I tried came up with the same result:
Data Source was PowerQuery to a SharePoint List.
As stated in the initial issue / question, when run independently the data all shows and displays as expected. It's only when run through a Power Automate Flow that the data doesn't appear.
So the fix...
The only thing that worked was to change the data source from PowerQuery to a Power BI Semantic Model.
This has a number of further limitations as the flow then needs to refresh the dataset (which is pointed at the SPO List) before it processess the Paginated Report - but it has resolved the issue.
Not ideal - but its working.
Hope this helps anyone else that has a similar issue moving forward!
Thanks
Dan
Hi, @tieva_dan
You need to make sure that all parameters are correctly passed from Power Automate to the paginated report. Sometimes, parameters may not be mapped correctly or missing, resulting in incomplete data rendering. Also verify that the data in the SharePoint list is refreshed and accessible when the report is generated. There may be latency or synchronization issues that cause the data to not be fully available.
Because your reports contain sub-reports, make sure they are properly linked and satisfy their data dependencies when you run the report through Power Automate.
You can check the following links:
Export paginated reports with Power Automate - Power BI | Microsoft Learn
Solved: Power Automate "export to file for paginated repor... - Microsoft Fabric Community
How to Get Your Question Answered Quickly
Best Regards
Yongkang Hua
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
38 | |
27 | |
17 | |
16 | |
8 |
User | Count |
---|---|
45 | |
38 | |
35 | |
17 | |
16 |