Forum Discussion
Embed Power App & Paginated Report Refreshing Issue
To achieve a complex reporting & commentary process, we implement the following:
- Power BI Paginated Report to directly read data from database and render the report
- Power App to writeback the Report Commentary (same commentary also part of above Paginated Report)
- Power BI Report PBIX (direct query mode) to have above two embedded and passed through the requried parameters
When Power App writeback the report comment, it invoke PowerBIIntegration.Refresh() to refresh to Power BI Report.
The embedded Paginated Report appears to be refreshing but the report comment does not refeclting the latest change.
By SQL Proflier (backend DB is SQL Server), it seems though the Paginated Reprot appears to be refreshing but as the report parameter does not changed, it display the snapshot data instead querying the backedn db to fetch the latest data.
Is there a way to enforce the embedded Paginated Report fetch the latest data from the back end database?
Hi cray_kuoYou could try by using the Power BI REST API to programmatically refresh the Paginated Report or clear its cache. This can be triggered when the commentary is updated in the Power App, ensuring the report fetches the latest data from the backend database. Additionally, try passing dynamic parameters (like a timestamp) to force the report to query the backend instead of using cached data.
If this post helped please do give a kudos and accept this as a solution
Thanks In Advance
2 Replies
Hi cray_kuoYou could try by using the Power BI REST API to programmatically refresh the Paginated Report or clear its cache. This can be triggered when the commentary is updated in the Power App, ensuring the report fetches the latest data from the backend database. Additionally, try passing dynamic parameters (like a timestamp) to force the report to query the backend instead of using cached data.
If this post helped please do give a kudos and accept this as a solution
Thanks In AdvanceThanks Akash_Varuna passing dynamic parameters (like a timestamp) to force the report to query the backend instead of using cached data is indeed a good idea
