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

Join us at the 2025 Microsoft Fabric Community Conference. March 31 - April 2, Las Vegas, Nevada. Use code FABINSIDER for $400 discount. Register now

Reply
Timbaaaal
Advocate II
Advocate II

Multiple Semantic Model created by Lakehouse - Cannot delete

Hi,

I published a dataflow Gen 2 yesterday which take data from 4 tables in one Lakehouse in order to create a new table in another LH (lets call it Gold).

The gold LH was new and never had any table. I think I might have created it while doing the destination mapping in the dataflow.

 

I now end up with 4 semantic model auto created (with no table) + the gold LH which had the table but no semantic model (Creation of SQL analytics endpoint/Semantic model was refreshing and my guess, stuck).

I deleted the gold LH, but cannot delete the 4 semantic model... Any thoughts?

 

Workspace is F2 capacity/West-Europe and is part of a development pipeline, but those items never got deployed.

 

PS: I am able to move them in a folder

 

Timbaaaal_0-1739531873342.png

 

Timbaaaal_1-1739531930533.png

 

 

 

4 REPLIES 4
v-csrikanth
Community Support
Community Support

Hi @Timbaaaal 
Thanks for using the Microsoft Fabric Community.
I replicated the scenario locally and was able to resolve it. The solution is deleting the dataflow that was originally created to map the destination of the Gold Lakehouse. Once the dataflow was removed, the unnecessary semantic models were no longer present, and the process functioned as expected. This suggests that the issue was caused by the initial dataflow's destination mapping, which, when deleted, resolved the problem.

If you found the above information helpful, we kindly request you to give us a Kudos and mark the response as the Accept as Solution.

Thank you,
Cheri Srikanth

Hi and thanks for looking into this.

I just deleted the dataflow, but the 4 semantic model (default) are still there.

This might due to the following (which was done prior deletion of the dataflow):

1. I was able to create a new Lakehouse with the exact same name

2. I reuse the same dataflow by updating the destination mapping to the new lakehouse

3. The old semantic model were moved to a different folder than the dataflow/new lakehouse

 

I have now also deleted the new lakehouse (which had the same name), but it still didn't delete those 4 semantics model.
However I am no longer able to create a new lakehouse with the same name. It still let me click on Create (Normally it doesn't), but I get error with "Lakehouse Id is not valid".

This is new, not sure if it because I deleted the dataflow or the last lakehouse..

 

Expected behaviour:

Timbaaaal_3-1739788674846.png

 

Current behaviour:

Timbaaaal_0-1739788324260.png

 

When clicking on Create:

Timbaaaal_1-1739788353367.png

 

Error Details:

Timbaaaal_2-1739788382344.png

 

 

 

 

StrategicSavvy
Resolver II
Resolver II

hi, you might be dealing with this isse:

https://community.fabric.microsoft.com/t5/Data-Engineering/HOW-TO-DELETE-default-semantic-model/m-p/...

 

it's said it is not possible to delete default semantic models

Hi, thanks for sharing.

I did came across this one as well. But in this case, the person is looking to delete the semantic model while keeping the lakehouse. looks like Microsoft doesn't want to have a Lakehouse without a semantic model (default), so this is expected behaviour.
In my case, I already deleted the original Lakehouse, but the SM didn't get deleted and on top of that I had multiple created when the Lakehouse got created by the dataflow.

 

But like people mentionned on the other post, underlying issue is that we should definitly have a way to delete artifacts in the workspace. But also full visibility (Staging, soft delete etc.) If they don't want us to mess up with dependencies, then they should put in place better control/visibility of dependencies, like they did with objects in Dynamics/Power Apps Solution.

Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!

FebFBC_Carousel

Fabric Monthly Update - February 2025

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

Feb2025 NL Carousel

Fabric Community Update - February 2025

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