Lakehouse creates (and recreates) multiple semantic models

[truls_sg]

Hi!
When creating a lakehouse named Silver, three semantic models named Silver are added. Two of those added models are not connected to the warehouse. I have tried to delete these models using the web UI and the fabric CLI. I have also deleted and recreated the warehouse, but the two orphaned semantic models pops back up. I am using Azure Devops Repos for source control. 

Found a similar problem here, but the accepted solution does not work for me becuase a) the orphans does not show up in the system storage pane, and b) when I delete the Lakehouse it is possible to delete the orphans via fabric CLI, but then when I recreate it the problem reappears.

Also copied the contents of the workspace to a new workspace that is not backed by GIT via deployment pipeline, and now I am facing the problem with my Bronze Lakehouse as well. This is a major problem because now, when trying to create a table, I get an "conflicting items" error referring to my redundant semantic models

Edit: This is what my OneLake catalog looks like:

 

 

[v-sathmakuri · Accepted solution]

Hi @truls_sg ,

Thank you for reaching out to Microsoft Fabric Community!!

Manually delete the Lakehouse from fabrics and follow these steps:

1. Go to your Azure DevOps repo.

2. Locate the file for orphan lake houses created during deployment.

The path will be similar to: /Lakehouses/Silver/semantic-model.

3. Manually delete the unwanted model folders/files that are not connected to a Lakehouse or Warehouse.

4. Commit and push your changes.

5. Re-deploy to ensure orphans are not created again.

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! 

Thank you!!

[truls_sg]

Seems to work! Thank you

[truls_sg]

Update: The create table issue went away when I disabled the lakehouse schemas preview