Forum Discussion
DirectLake Auto Refresh Error
tolgakurt updating the Semantic Model is the key step after making schema changes in your Fabric Lakehouse.
always Update the Schema in the Semantic Model After Schema Changes, Any time you rename, add, or remove columns in your Lakehouse table, make sure to refresh and update the dataset schema in Power BI.
Thanks,
Prashanth
MS Fabric community support
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query
Yes, I was doing some measure calculations with these columns. But that wasn't the problem. I found the solution while checking the settings in the semantic model. When we make a change in the dataset, we need to update these changes in the semantic model.
Semantic Model -> Open Data Model -> Edit Tables
When we do this and update the model, the error is resolved.
tolgakurt updating the Semantic Model is the key step after making schema changes in your Fabric Lakehouse.
always Update the Schema in the Semantic Model After Schema Changes, Any time you rename, add, or remove columns in your Lakehouse table, make sure to refresh and update the dataset schema in Power BI.
Thanks,
Prashanth
MS Fabric community support
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query
hi Prashanth, I had a very similar case related to this post. So appreciate if you can give me some advice.
I'm using pipeline to refresh sematic model, and before that will execute a store procedure which have some drop table and re-create table actions, I guess still the 'cache' is making problem, it occasionally encounter refresh failure, says not found table, but it do exist. I was use 'Wait' to let system auto synchronize schema, but it doestn't solve the problem, please do you have any better ideas?
Did you find a solution to this? I'm having the same issue.
Hi PJ, no perfect solution, I've reached out to MS support, they said becasue wh use delta table underlying so drop table is not recommended, then I altered my SP use truncate data instead, kind solved by this way.
