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

Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Learn more

Reply
Frank1
Frequent Visitor

Cannot auto refresh imported dataset

After

1) creating an Azure SQL Direct Query report in PBI Desktop,

2)  then publishing,

3)  then converting the dataset to Import Mode, using PBI desktop

4) re-publishing

 

automatic refresh on the dataset does not available and manual refresh does not update anything. The published dataset continues to identify as Direct Query, even with imported cached data.

1 ACCEPTED SOLUTION
v-qiuyu-msft
Community Support
Community Support

Hi @Frank1,

 

Based on my test, after change mode from DirectQuery to Import and republish the report to service, the dataset still keeps in DirectQuery mode and schedule refresh is not available. But once we remove the original dataset then publish the report, schedule refresh is available in dataset.

 

For this issue, I will report it internally and back here once get any feedback. In your scenario,m you can remove dataset and publish report again to work around the issue temporarily.

 

Best Regards,

Qiuyun Yu

Community Support Team _ Qiuyun Yu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

View solution in original post

3 REPLIES 3
v-qiuyu-msft
Community Support
Community Support

Hi @Frank1,

 

Based on my test, after change mode from DirectQuery to Import and republish the report to service, the dataset still keeps in DirectQuery mode and schedule refresh is not available. But once we remove the original dataset then publish the report, schedule refresh is available in dataset.

 

For this issue, I will report it internally and back here once get any feedback. In your scenario,m you can remove dataset and publish report again to work around the issue temporarily.

 

Best Regards,

Qiuyun Yu

Community Support Team _ Qiuyun Yu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Hi @v-qiuyu-msft

 

Thanks, I confirm this and also that another workaround is to rename the report in PBI Desktop (thus dataset), reimport and republish.

 

Best Regards

Frank

Seth_C_Bauer
Community Champion
Community Champion

@Frank1 Have you tried to delete the dataset and republish? I realize this isn't optimal, and may not  be possible depending on how the report is being shared... But I would imagine that there is some cached element on the dataset in the Service side...

 


Looking for more Power BI tips, tricks & tools? Check out PowerBI.tips the site I co-own with Mike Carlo. Also, if you are near SE WI? Join our PUG Milwaukee Brew City PUG

Helpful resources

Announcements
Fabric Data Days Carousel

Fabric Data Days

Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!

October Power BI Update Carousel

Power BI Monthly Update - October 2025

Check out the October 2025 Power BI update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors