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

Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.

Reply
Ostrzak
New Contributor III

Problems with refreshing of semantic model

Hi,

 

I have problems with refreshing a semantic model that is based on an existing lakehouse. As a part of a bigger pipeline, after overwriting delta tables in a lakehouse, a semantic model refresh takes place. 

 

Now, although the refresh shows up as succesful, reports feeding on this semantic model do not refresh. 

 

I tried turning off and on the Direct Lake connection for that semantic model. Additionally, I tried selecting tables for the model. It didn't help. I tried refreshing the sql endpoint of the lakehouse. 

None of these actions helped.

 

Now I'm working on a default semantic model, but its customization is limited. I would rather have a separate semantic model that properly refreshes.

 

Thank you in advance for any help.

1 ACCEPTED SOLUTION
Ostrzak
New Contributor III

Hey,

 

As I mentioned, I was working in a "separate" semantic model, so not the default semantic model. I didn't have problems with default model, but I used it only as a temporary solution.

 

On the next day semantic model refreshed properly. I assume it was some backend issue. It works now.

View solution in original post

3 REPLIES 3
Anonymous
Not applicable

Hi @Ostrzak ,
You can try the following steps to solve the problem:
1. Try refreshing the semantic model manually to see if this solves the problem.
2. You are using the default semantic model, make sure the โ€˜Sync the default Power BI semantic  modelโ€™ setting is turned on.

vyifanwmsft_0-1721181690883.pngvyifanwmsft_1-1721181728075.png

vyifanwmsft_2-1721181760451.png

Best Regards,

Ada Wang

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

Ostrzak
New Contributor III

Hey,

 

As I mentioned, I was working in a "separate" semantic model, so not the default semantic model. I didn't have problems with default model, but I used it only as a temporary solution.

 

On the next day semantic model refreshed properly. I assume it was some backend issue. It works now.

Anonymous
Not applicable

Hi @Ostrzak ,

Anyway, glad to hear you've sorted things out.

 

Best Regards,

Ada Wang

Helpful resources

Announcements
Users online (27)