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

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
balafbm
Advocate I
Advocate I

Lakehouse Table schema change does not reflect in Custom Direct Lake semantic model

Hi

I have multiple tables in my Lakehouse. Inside the Lakehouse, I clicked on the "New semantic model" option to create a direct lake semantic model, import the tables and create relationships.

Later, one of the tables required additional columns, so I altered the schema in the Lakehouse to add the additional columns.

After adding these additional columns, the semantic model does not reflect these new additions by default.

I will have to "remove" the table from the model and re-add the table, and only then these new columns are visible in the table.

 

This is a huge problem, especially when I have to recreate the table relationships all over again given that it is a FACT table.

 

I have read this blog post from Microsoft: https://powerbi.microsoft.com/en-in/blog/improvements-for-creating-new-direct-lake-semantic-models/ which says that "In custom Direct Lake models, schema changes are not updated automatically without user intervention. This behavior is comparable to import and DirectQuery semantic models in Power BI."

This does not make any sense.

Why should I remove, re-add and create the relationships again just because of schema changes (additional columns) in the table?

 

 

 

 

1 ACCEPTED SOLUTION

My bad.

I believe this has been fixed.

Link to the documentation: https://learn.microsoft.com/en-us/fabric/fundamentals/direct-lake-edit-tables#editing-a-semantic-mod...

 

pic.png

We need to open the "Edit Tables" dialog. Click on the "refresh icon" and then click "Confirm".

This is now reflecting the additional columns. 

View solution in original post

4 REPLIES 4
spaceman127
Helper II
Helper II

Hi @balafbm 

the article that @v-saisrao-msft  adds in his post describes this quite accurately. You basically just need to update the schema and your changes should be reflected.
Deleting and recreating the relationships is not necessary.

 

Best regards

v-saisrao-msft
Community Support
Community Support

Hi @balafbm,

Thank you for reaching out to the Microsoft Fabric Forum Community.

Since this is a known limitation, I suggest submitting it to the Microsoft Fabric Ideas forum. If it receives enough votes, the product team might include it in a future update.

Fabric Ideas - Microsoft Fabric Community

 

Edit tables for Direct Lake semantic models - Microsoft Fabric | Microsoft Learn

Hope this helps

 

Thank you.

My bad.

I believe this has been fixed.

Link to the documentation: https://learn.microsoft.com/en-us/fabric/fundamentals/direct-lake-edit-tables#editing-a-semantic-mod...

 

pic.png

We need to open the "Edit Tables" dialog. Click on the "refresh icon" and then click "Confirm".

This is now reflecting the additional columns. 

Hi @balafbm,

Thank you for your insights. Please mark your helpful reply as the solution so it can assist other community members facing the same issue.

 

Helpful resources

Announcements
Fabric July 2025 Monthly Update Carousel

Fabric Monthly Update - July 2025

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

August 2025 community update carousel

Fabric Community Update - August 2025

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