Forum Discussion
Semantic Model not refreshing in Power Bi Service
leafrancis95 If you're using Import mode and refreshing manually in Desktop, this message can safely be ignored just make sure refresh is disabled in the service, and you're good:
- Navigate to your Workspace where the dataset/report is published
- In the workspace, Find the Dataset and click the ellipsis
- What do you see under these sections?
- Data Source Credentials
- Scheduled Refresh
Did it work? đź‘Ť A kudos would be appreciated
🟨 Mark it as a solution to help spread knowledge 💡
Hi leafrancis95
Power BI does not auto-refresh datasets after publishing if they use a local source with no gateway. That’s why you’re seeing this new message.
To fix it, either set up an on-premises data gateway so the service can access your local SQL Server, or keep publishing manually and turn off refresh in the service to stop the errors.
Did it work? đź‘Ť A kudos would be appreciated
🟨 Mark it as a solution to help spread knowledge 💡
Thanks for the reply.
Unfortunately, setting up an on-premise data gateway is not an option so I'll need to continue manual refresh.
I've never turned on the refresh options in Service and nothing seems active right now, so I'm not sure how to turn it off. Where should I be looking for turn it off ?
leafrancis95, kindly refer to the documentation provided.
leafrancis95 If you're using Import mode and refreshing manually in Desktop, this message can safely be ignored just make sure refresh is disabled in the service, and you're good:
- Navigate to your Workspace where the dataset/report is published
- In the workspace, Find the Dataset and click the ellipsis
- What do you see under these sections?
- Data Source Credentials
- Scheduled Refresh
Did it work? đź‘Ť A kudos would be appreciated
🟨 Mark it as a solution to help spread knowledge 💡I don't have a Data Source credentials option, likely because the semantic model is not using cloud or gateway-connected data sources that require credentials.
Scheduled refresh is deactivated...It turns out this was a widespread issue on Microsoft’s end. The problem has been resolved over the weekend. Thanks for your help!
