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

View all the Fabric Data Days sessions on demand. View schedule

Reply
FotFly
Helper II
Helper II

Power BI semantic model refresh fails.

Hi,

I published a report to the Power BI service yesterday and when I hit the On demand refresh button I get the following error.
The thing is that the project refreshes on Power BI desktop but not in service. All data come from SQL tables and all datasource credentials are updated in service. The table that is mentioned at the end, and I have hidden for confidentiality reasons, has no problem running in any other projects.

It will be really helpful if you had an idea of why this might happening.

Thanks in advance
FotFly_0-1724252574807.png

 

6 REPLIES 6
Tutu_in_YYC
Super User
Super User

There are certain transformation that work in power bi desktop but not in power bi service. Can you narrow down to which table/query is causing the problem, and elaborate on how that query is created?

Even if the error message specifies table X, sometimes it is not true. But try removing table X from the model, republish/refresh and see if that is the query that is giving you issues.

Hi,

Thank you for your reply.
I did remove the query and reuploaded the report and it refreshes without issues this time. However, this should not be happening. The query gets data from an sql table and then I just perform a merge with another query to filter out some rows. This is a common practice and I do not understand why it causes that issue.

Odd... but just fyi, another reason why a merge doesnt work in the service is when the tables/query/data source have different privacy settings.

Yeah, i thought of that too, but I doubled checked and have set both to the same provacy level. Even tried the ignore privacy levels but did not work.

just for fun, can you do a dummy merge with queries that are in the working report? See if that work.. Like you said, merge is a common practice.

Hi, I found the solution. There was another merge on the second table that messed with the merge to my initial query. Again, that third query had the same privacy settings as the other two. So, I took the second query and kept it plain without the extra merge I was performing, merged it to my main query and then created a reference to merge that second query with the third one that was causing the problem. The thing is that these merges have been applied to other projects without any issues but in this one I had to find this work around.

Thanks again for your help.

Helpful resources

Announcements
November Power BI Update Carousel

Power BI Monthly Update - November 2025

Check out the November 2025 Power BI update to learn about new features.

Fabric Data Days Carousel

Fabric Data Days

Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors