Forum Discussion

KTowerPower's avatar
KTowerPower
Regular Visitor
3 months ago
Solved

Fabric Semantic Model Updates No Longer Displaying

Hello all!

 

I've been making a good few edits to my Semantic Model recently, which has led me to refresh my data and schema (through the Edit Tables button) a lot. After a while, it just stopped updating for me.

 

So, I was adding some new columns to one of my tables, which were correctly added to my Lakehouse and SQL Analytics Endpoint, but these columns have not appeared in Semantic Model after numerous attempts. Here is what I've tried thus far:

 

  • Refreshing the tables (Edit Tables Button)
  • Refreshing the Semantic Model & Edit Tables
  • Deleting the table from the Semantic Model and adding it back
  • Removed and added back ALL of my tables in the Semantic Model
  • Rerunning the notebooks for the table itself
  • Running a notebook that runs ALL my tables in the Gold Layer (I use a Medalion Schema)
  • Adding multiple simpler columns to various tables (ALL of which are not displaying in my Semantic Model)

Has anyone else been experiencing any issues like this? Or did I mess something up along the way?

 

I appreicate any feedback you all have. I will most likely open a support ticket on this as well if this continues.

 

Thanks!

  • Thank you to all! Thankfully, I was able to create a new Semantic Model with my changes and it has been working so far. I'm still unsure about why the original Semantic Model decided to not function properly, but tayloramy brings up a great point. I may look into finding other ways to fully refresh the metadata if I have some spare time. Although, for now, my problem has been solved. Thanks again to all who helped out!

5 Replies

  • Thank you to all! Thankfully, I was able to create a new Semantic Model with my changes and it has been working so far. I'm still unsure about why the original Semantic Model decided to not function properly, but tayloramy brings up a great point. I may look into finding other ways to fully refresh the metadata if I have some spare time. Although, for now, my problem has been solved. Thanks again to all who helped out!

  • Hi KTowerPower 

     

    I think this is wondering. You follwed all correct steps. But you're facing the issue. Make sure to check , your newly added columns is visble in Lakehosuer tbale and SQL analytics endpoint. If it is not vsible in semtic model it means that issue might  be meta data synchrnisation. 

     

    So, pls check first if your newly added columns is available in lakehouse--> SQL anlytics endpoint and then it hsould visble in semantic model. If not please raise a Mcirosoft Support ticket. 

     

    Please read thireds https://community.fabric.microsoft.com/t5/Fabric-platform/New-column-added-to-Lakehouse-table-not-appearing-in-Semantic/m-p/4927147

    https://community.fabric.microsoft.com/t5/Service/Adding-a-column-to-a-Fabric-sematic-model-table/m-p/3595167

     

    whihc might faced similar kind of issue, whihc might helps you.

     

    Thank you!

     

    Did I answer your question? Mark my post as a solution!

    Proud to be a Super User!

  • Thank you to trivedisunita and suparnababu8! I'm currently in the process of making another semantic model to see if that's the issue. Otherwise, I have tried other options, including remaking the entire table with the new columns, which is also still ongoing. I'll be checking in on these today, and if these don't work, I'll be placing a support ticket. I'll also make sure to post any solutions I find and accept them as the solution. Thanks again!

  • trivedisunita's avatar
    trivedisunita
    Icon for Continued Contributor rankContinued Contributor

    Hi KTowerPower ,

     

    From what you have described, you have already worked through most of the common troubleshooting steps. 

    Since the new column are visible in both the Lakehouse and the SQL Endpoint , i would expect Edit tables to pick up those schema changes. if it isn't, first verify that the semantic model is connected to the expected SQL Analytics Endpoint.

     

    You could also try creating a new sematic model from the same Lakehouse, if the new columns appear there, it would help to determine whether the issue is specific to the existing semantic model.

    If the behavior is the same with a new semantic model, it may be worth opening a support ticket.

     

    If this reply helps you consider marking it as a solution.

     

    Thanks

     

     

     

  • Hi KTowerPower, 

    I've noticed that sometimes a full metadata refresh of the lakehouse SQL endpoint is needed for the table changes to be recongised when you edit the model. 
    Also note that the tables will not update automatically, you need to edit the tables, then click the refresh button at the top, then click ok.