Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
We are using Incremental Refresh, and intend to use REST API to trigger dataset refreshes.
We found that the "Effective Date" applied during a manual refresh is based on UTC time. Because of this, and with incremental refresh we effectively lose a day of data for several hours of the day (we are on UTC +12 timezone).
We noticed that when we enable Scheduled Refresh on Power BI Service and specify the Local Time Zone, any subsequent manual refreshes with REST API will pull the correct date range of data. However, this introduces an unwanted Scheduled Refresh.
Is there any way to trigger the refresh using the correct Local Time Zone, without having to enable Scheduled Refresh?
Or is there something we are missing?
hi Lionel,
From the link you have provided there does not seem to be any mention of specifying the time zone info.
I know you can stick the LocalTimeZoneId in when configuring the refresh schedule
But the refresh API does not seem to offer any thing similar.
We have decided to pursue using TMSL to kick of the refresh, which offers the option of specifying effective date.
Hi @bongmw ,
The refresh time needs to be defined by code in the script. You can use the code to specify the time as the local time, so this problem does not exist.
You can use PowerShell to call the API.
Refreshing all datasets in Power BI using REST API (technovert.com)
Best regards,
Lionel Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
11 | |
6 | |
4 | |
2 | |
2 |
User | Count |
---|---|
4 | |
3 | |
3 | |
3 | |
3 |