Don't miss your chance to take exam DP-600 or DP-700 on us!
Request nowLearn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
Hello everyone,
I’m working on a Power BI report that retrieves data from REST APIs. The problem is that the dataset has grown too large, and the API server can’t handle returning all records during refresh, even with pagination enabled.
I considered using Incremental Refresh, but it still requires a full initial refresh after publishing to create the partitions — and that initial load fails due to data volume limitations.
I want to know if there is any approach where Power BI can append only the newly updated daily data, without requiring a full refresh of all historical data every time.
Thanks in advance.
Solved! Go to Solution.
Extract the REST API data into JSON, CSV, or Parquet files as needed (including re-fetching if changes happened). Store the result in OneLake or another suitable file store (SharePoint works in a pinch)
Ingest all the data, or access it via Direct Lake, or construct your own incremental refresh - up to personal preferences
If the partitions grow too big, use (fake) incremental refresh with bootstrapping and XMLA refresh processes.
Troubleshoot incremental refresh and real-time data - Power BI | Microsoft Learn
Hi @dsvansh,
Just following up to see if the Response provided by community members were helpful in addressing the issue. if the issue still persists Feel free to reach out if you need any further clarification or assistance.
Best regards,
Prasanna Kumar
Hi @dsvansh,
Thank you for reaching out to the Microsoft Fabric Forum Community, and special thanks to @GilbertQ and @lbendlin for prompt and helpful responses.
Just following up to see if the Response provided by community members were helpful in addressing the issue. if the issue still persists Feel free to reach out if you need any further clarification or assistance.
Best regards,
Prasanna Kumar
Extract the REST API data into JSON, CSV, or Parquet files as needed (including re-fetching if changes happened). Store the result in OneLake or another suitable file store (SharePoint works in a pinch)
Ingest all the data, or access it via Direct Lake, or construct your own incremental refresh - up to personal preferences
If the partitions grow too big, use (fake) incremental refresh with bootstrapping and XMLA refresh processes.
Troubleshoot incremental refresh and real-time data - Power BI | Microsoft Learn
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.