New Column Not Showing Up In Semantic Model

[esjetmore]

Hello all! I have a SQL database in Fabric and a table called "tick". I have used the following to add a column to that table. When I run this code in the SQL endpoint it fails, but if I run it in the SQL database, it works and I can query the table and see the new column in there.

alter table dbo.tick
add [k_times]
as concat(order_date, order_code, tkt_code)

However, when I try to access the new column within my semantic model, it is not visible. I've tried refreshing the model and I've tried this solution as well with no success. 

Should I be doing this differently? All I am trying to do is add a column to an existing table without having to drop the table (as I will lose all my modeled relationships and measures). Thank you!

[joeguicearnold]

Were you ever able to get this resolved.  We are having the same issue, where a new column is in the SQL table but not available in the SQL Endpoint or any of the semantic models.

[esjetmore]

No. I spoke with Microsoft support and calculated columns added through the SQL database are currently not supported.

[v-nmadadi-msft]

Hi @esjetmore ,

We really appreciate your efforts and letting us know the update on the issue.

Please continue using fabric community forum for your further assistance.

Thanks and Regards

[NimaiAhluwalia]

Hello @esjetmore 

 if the below columns are in the table tick than isnstead of adding it separetlty by using an endpoint or even it does not appear in the model after your refresh the model you can create a calculated column in power bi as a workaround, as many people are facing this issue this might be a glitch from fabric's end.

(order_date, order_code, tkt_code

[esjetmore]

My data is in Direct Lake mode, so that is not possible. Calculated columns are not available for that connection type. https://learn.microsoft.com/en-us/fabric/fundamentals/direct-lake-overview

[NimaiAhluwalia]

Hello @esjetmore 

Thanks for mentioning that, you can try using the direct query mode, obviously you wont be able to create a column in this mode as well but worth trying if the data is getting pulled properly, but if your data size is not to large you can use the import mode as well which gives you more flexibility to model and transform the data in the power bi, than you can try concatinate the columns as a calculated column.

[esjetmore]

Our data size is large and updates every 20 minutes. We can't use import mode, and direct query does not solve our problem either. Is there really no way to do this? Adding a column to an existing table seems like basic functionality.

[v-nmadadi-msft]

Hi @esjetmore  ,
Thanks for reaching out to the Microsoft fabric community forum.
It is not executing in SQL analytics endpoint because it functions as read only mode that means that Data Definition Language (DDL) statements such as create table, alter table and drop table are not supported. This endpoint is designed primarily for querying and analysing data, rather than modifying its structure.
What is the SQL analytics endpoint for a lakehouse? - Microsoft Fabric | Microsoft Learn

For the Semantic model part, try to create a new semantic model to check if the new column gets included

Please review the limitations document to identify any potential conflicts affecting the semantic model update:
Limitations for SQL database (preview) - Microsoft Fabric | Microsoft Learn

If you find this post helpful, please mark it as an "Accept as Solution" and consider giving a KUDOS.
Thanks and Regards

[esjetmore]

Thank you for the response! I don't need the ALTER TABLE to run in the SQL endpoint because I was already able to get it to run in the SQL database. In the SQL database the new column "k_times" is visible:

But in the SQL Analytics Endpoint, it still does not appear: 

In the new semantic model I created, the new column is also missing. I reviewed the documentation you shared and there is no information regarding semantic model shifts or the creation of new columns that would effect this.

Can you recommend an alternative way of creating a new column in an existing delta table without dropping the table?

[v-nmadadi-msft · Accepted solution]

Hi @esjetmore ,
Sorry to know it didn’t help. Its most likely an unintended bug. Please consider reaching out to Microsoft Support. You can provide them with all the troubleshooting steps you've already taken, which will help them understand the issue better and provide a resolution. They might be able to identify something specific about your admin account setup or provide a solution that isn't immediately obvious. 

Below is the link to create Microsoft Support ticket:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

Thanks and Regards