Unable to edit Semantic Model with Direct Lake over SQL Lakehouse

[debiagui]

We have a Semantic Model connected to a Lakehouse using Direct Lake via the SQL Endpoint.

The model has been working properly; however, today the “Edit tables” option is unexpectedly disabled.

We can still refresh the model without any issues, query the SQL Endpoint successfully, and navigate the Parquet files through OneLake Explorer. Additionally, we’re able to create parameters and calculated columns within the Semantic Model — everything else appears to be functioning correctly.

For reference, I am the owner of both the Semantic Model and the Lakehouse.

We tried to create a new semantic model as test but fails:

[BhaveshPatel]

Hi @debiagui 

You should create a Microsoft Suppot Ticket and explain about Semantic Model and Direct Lake.

[AntoineW · Accepted solution]

Hello @debiagui,

If any of the following happened in the Lakehouse:

• The SQL Endpoint was renamed,

• A table was deleted or replaced,

• The Lakehouse folder structure changed (e.g., new folders under /Tables),
  then the binding between the semantic model and its data source can break partially.

👉 In this case, “Edit tables” gets disabled because Fabric can’t safely open the table-mapping dialog while schema metadata is inconsistent.

Sometimes, it's a bug interface, the button "Edit Tables" can be grayed and the solution is to click on a table in your model semantic, and the button will appear clickable. 

Hope it can help you !

Best regards,

Antoine