Scheduled Refresh
Power BI · Power BI Service
Theory
An imported semantic model holds a copy of the data, so it must be refreshed to show new rows. In the Service you open the semantic model's settings, confirm the data source credentials, and turn on scheduled refresh with a frequency (daily or weekly), one or more time slots and a time zone. Each refresh re-runs all Power Query steps, reloads the tables and recalculates calculated columns and tables. You can also click Refresh now for an on-demand refresh.
Sources in the cloud, such as Azure SQL Database or SharePoint Online files, can usually refresh directly. On-premises sources, such as a SQL Server in the office or a file on a local drive, need an on-premises data gateway. Refresh history shows each run's status and errors, and failure notifications can be emailed to the owner. DirectQuery and live connection models do not need data refresh because they query the source directly.
Why we use it
Reports are only useful if the numbers are current. Scheduled refresh removes the manual 'open Desktop and refresh' step and keeps everyone looking at the same up-to-date data.
When to use it
Set it for every published Import model. Choose times after the source data loads (for example after the nightly ETL). For very large tables, combine it with incremental refresh; for near real-time needs, consider DirectQuery.
How it works
- Scheduled time arrives
- Service connects using stored credentials
- Is the source on-premises? Yes: Route through the data gateway. No: Connect to the cloud source directly.
- Re-run Power Query steps and reload tables
- Did refresh succeed? Yes: Report shows new data. No: Owner gets a failure notification.
- Next scheduled run
Syntax
Service → Workspace → semantic model → ... → Settings
Data source credentials → Edit credentials
Gateway and cloud connections → map sources (on-premises)
Refresh → Configure a refresh schedule: On, Daily/Weekly, time slots, time zone
Refresh history: semantic model → ... → Refresh historyExample
1. Warehouse ETL finishes loading Sales at 6:00 AM.
2. Semantic model 'Sales Overview' → Settings → Refresh: On.
3. Frequency: Daily; times 7:00 AM and 1:00 PM; time zone UTC+05:30.
4. Tick 'Send refresh failure notifications to the semantic model owner'.
5. Next morning, Refresh history shows Completed; the report now includes yesterday's orders.Key points
- Import models need refresh; DirectQuery and live connections do not
- Credentials must be set before refresh can run
- On-premises sources require a data gateway
- Schedule after upstream data loads finish
- Check Refresh history and enable failure notifications