Forum Discussion
Semantic model refresh does not refresh data in report
- 10 months ago
I think I may have a solution... I've added a step to hit the endpoint with a simple query before refreshing my model, looks like it might do the trick.
You may want to follow my thread on the subject here: https://community.fabric.microsoft.com/t5/Service/Semantic-Model-connected-to-Lakehouse-SQL-Analytics-endpoint-not/m-p/4828558/highlight/false#M286453
This morning I came to my laptop, and controlled if the pipeline ran and if I have the latest data in the Lakehouse.
The pipeline succeeded (including the Refresh Semantic Model activity) and I had the latest data in my Lakehouse.
When I opened the report (which has the semantic model as the data source) the report showed the old data, so I explored the data in the semantic model which also had the old data in it, even though the pipeline "refreshed" it and the Refreshed column showed the correct date as per the pipeline run refresh.
Then I clicked on the Refresh now button in the Semantic Model and voilá, the Semantic Model and the report both show the latest data.
My bottom line is, that whichever method I choose (be it a Semantic Model Refresh activity in a pipeline, or a scheduled semantic model refresh) to automatically refresh the Semantic Model, even though I see that it has been refreshed on paper, in reality the data is not refreshed.
Manually refreshing the Semantic Model on the other hand usually works, but it sucks to have to refresh all my Semantic Models manually every day if i want to keep my reports up to date.
I don´t think that automatically refreshing a Semantic Model should be so complex or prone to error, so I wonder:
- Is it only me who experiences problems with automatically refreshing the semantic models?
- Am I missing something?
- Is automaticall refreshing a Semantic Model a sort of black magic?
Please let me know if you also face this problem, and please let me know how you do automatic Semantic Model refreshes yourself.