Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Join us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered

Close, Apply, and Refresh All

I'd like to propose the addition of a "Close, Apply, and Refresh All" option within the Transform Data panel in Power BI Desktop.

 

As part of our ongoing cost-efficiency initiative, we’ve transitioned our enterprise cube into Power BI data models, leveraging native queries and query folding to optimize performance. With incremental refresh enabled, we must update the RangeStart and RangeEnd parameters and refresh all data prior to publishing. This step is critical—if skipped, the web-based Power BI service initiates a full refresh post-publish, resulting in a 30–60 minute lag where visuals may appear blank or error-prone, disrupting the user experience.

 

Currently, after updating the parameters and selecting Close & Apply, only the tables with incremental refresh configured are updated. To fully synchronize the model, we must then manually trigger a second refresh for the remaining tables—effectively doubling the wait time.

 

Introducing a "Close, Apply, and Refresh All" option would streamline this workflow by consolidating both steps into one. This enhancement would:

  • Reduce total refresh time and manual intervention.
  • Improve publishing efficiency.
  • Minimize front-end disruption for report consumers.

 

This small UX improvement could yield significant time savings and operational consistency for teams working with complex, parameter-driven models.

Status: New
Comments
kleigh
Resolver IV
This is absolutely needed. It's too easy to get the dashboard in an invalid state, where some tables are refreshed, but not others. For example: 1) Refresh on desktop. 2) There is an error which needs fixing in Power Query. 3) Fix error. 4) Tables which were fixed refresh, but the other tables are excluded. If you're not paying attention, the data can *appear* to have refreshed as a main table updated. If you are paying attention, it's just a frustration to have to refresh twice with no way to get it right first time.