Report and semantic model stored published on different workspace - semantic model refresh disabled

[HSZU]

I have a semantic model published on one workspace. Then I created a report basen on that semantic model and publish it on differnent workspace.

Report is used by the users - I can see report views in usage metrics.

However, data refresh of semantic model has been disabled and the reason was "No one has viewed dashboards or reports built using this semantic model for two months. To resume it, just visit a report or dashboard built using this semantic model or manually refresh the semantic model using the Refresh Now option."

Does anybody know how to solve this issue?

I enabled data refresh again but how to avoid it in the future?

[Anonymous]

Hi @HSZU ,

You just need to reopen it for use, no other additional action is required:

Configure scheduled refresh - Power BI | Microsoft Learn

Hope it helps!

Best regards,
Community Support Team_ Scott Chang

If this post helps then please consider Accept it as the solution to help the other members find it more quickly.

[HSZU]

I know that but the thing is that report that is built on this semantic model is used very often. The only unusual thing is that model is published on one workspace and report on different workspace. 

I do not want to enable semantic model refresh every two months.

[aj1973]

Hi @HSZU 

Technically this could be a bug in the dataset or more likely a failure as shown in here

Maybe, before rerunning the refresh in the service it is wiser to open the Power Query of the dataset in the Desktop to identify where the failure is coming from.

[Shivu-2000]

Hi @HSZU,

Since you've already re-enabled data refresh, your semantic model should be updating again.

But to avoid problem in future please ensure that:

1. Scheduled Refresh: Set up a scheduled refresh for the semantic model in the workspace where it's published. This ensures automatic updates regardless of report views.

2. Regular Report Access

3. Gateway Configuration: Ensure a data gateway is configured correctly if your data source resides on-premises and requires a gateway for refresh.

If you find this insightful, please provide a Kudo and accept this as a solution.