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

Join us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered

Reply
jimmy101
Frequent Visitor

Error in Semantic Model After Table Upsert

I have data flowing as showin the diagram below on Image 1.  When I do the upsert to the Fabric Warehouse table with 50M rows and refresh the Semantic model, simply getting a sum on a column fails as shown on Image 2.  Other smaller tables within the model that follow the same process work well.  I try running a simple query on DAX Studio and get the error shown in Image 3.  In order to remediate the issue, I have to recreate the table with the SQL steps shown in Image 4.  After I recreate the table in the warehouse within Workspace A with the sql as shown on image 4 everything works fine until the next I complete the upsert process. 

 

I am completing the upsert by bringing the source data into a staging table for records whose modified date is greater than the max modified data on the target table.  Once the new data is loaded on the staging table, I locate any matching (modified) records in the target table and delete them.  Finally insert all records in the staging table onto the target table.  This issue seems to be new and is preventing this solution from going to production.

 

Image 1

jimmy101_0-1709572795515.png

Image 2

jimmy101_1-1709572885080.png

 

Image 3

jimmy101_2-1709573002801.png

 

Image 4

jimmy101_0-1709573489797.png

 

 

 

 

 

4 REPLIES 4
AndyDDC
Super User
Super User

Not sure if it'll make a difference but could you do a CLONE instead of the SELECT * INTO. So clone the fact temp back to the fact. Just to see if there's any metadata issue with the underlying Delta.

 

sp_rename works too

I tried doing the CLONE instead of recreating the table with the SELECT * INTO but that failed to resolve the issue.  

 

Hi @jimmy101 

 

Thanks for using Microsoft Fabric Community.

Apologies for the delay in response from my end and for the inconvenience that you are facing here.

It's difficult to tell what could be the reason for this performance. I would suggest you to create a support ticket. This is the most direct way to get official assistance and specific insights into your situation. The support team can do a thorough investigation on why this it is happening and suggest solutions.

Please go ahead and raise a support ticket to reach our support team:

https://support.fabric.microsoft.com/support
Please provide the ticket number here as we can keep an eye on it.

 

Thanks

Hi @jimmy101 

 

We haven’t heard from you on the last response and was just checking back to see if you've had a chance to submit a support ticket. If you have, a reference to the ticket number would be greatly appreciated. This will allow us to track the progress of your request and ensure you receive the most efficient support possible.

 

Thanks.

Helpful resources

Announcements
May FBC25 Carousel

Fabric Monthly Update - May 2025

Check out the May 2025 Fabric update to learn about new features.

June 2025 community update carousel

Fabric Community Update - June 2025

Find out what's new and trending in the Fabric community.