Also using a notebook to create a Lakehouse based on import sempy.fabric as fabric
It creates default semantic models outside the normal structure of Lakehouse creation like
--- LakehouseName
----- SemanticModelName
Example:
--- Lakehouse1
---- Lakehouse1
When you now delete the Lakehouse also the default semantic model is deleted.
To somekind of reason the sempy.fabric.create_lakehouse does create the default Semanticmodel not in this structure and when deleting the Lakehouse the semanticmodel still exists.
Needing to delete the workspace to remove it.
No issue for development but can not be done in production workspaces.
With sempy.fabric it also was possible to end with multiple semanticmodels having the same name, seeing in my development workspace:
Lakehouse3
Lakehouse3
Lakehouse3
Recent ideas
Enable Fine-Grained, Least-Privilege Control Over Fabric Artifact Creation
Please introduce more granular permission controls that allow admins to determine which user groups can create specific Fabric artifacts. The current all-or-nothing model—where users can either creat...krish0073 hours agoNew MemberNew158Views2likes1CommentMS Fabric User Permission Segmentation by Artifacts
Currently, when we grant users permission to create Fabric artifacts, they can create anything available in the workspaces they have access to. This unrestricted access can lead to an unstructured en...Anonymous3 hours agoNot applicableNew324Views8likes2CommentsNew Monitor Experience - Color Blind Friendly Option
The "Run history" column relies solely on red/green to indicate success/failure, which isn't colorblind-friendly. I'd suggest adding an option to use a colorblind-safe palette (e.g., blue/orange) and...ericpe5 hours agoRegular VisitorNew7Views0likes0Comments