We recently had an issue that ground our production Fabric to a halt. A user had added 2 semantic models with the same name (Table was the name - boo!). These semantic models were unrelated to the lake house that was connected to the notebook. Every time you tried to interact with the connected lake house by either spark.sql("select from table") or saveAsTable, it would throw a duplicate object error. It was not immediatly obvious what the problem was.
After renaming on of these semantic models, (Table_new) things started working again.
Idea:
Fabric should not allow semantic models with the same name to be allowed within a workspace. This functionality already works within the Lake House. You cannot have two tables with the same name.
There should be object creation logic to dis-allow objects (semantic models) to be added that already exist.
on:
Pattern Based Visuals Formatting for accessibility
on:
Put back the Other Contacts check box for dataflow...
ToddChitt
on:
(dynamic) Connection's in Copy data activity broke...
on:
Conditional formatting in row header in Matrix tab...