Inconsistent Schema Prefix Behavior in Fabric Lakehouse Semantic Model

Hi all,

I'm working with a schema-enabled Microsoft Fabric Lakehouse, and I've noticed some inconsistent behavior regarding schema prefixes when accessing tables through the semantic model and notebooks.

Scenario:

My lakehouse contains multiple schemas, and many tables are organized under those schemas.
When viewing the semantic model, I’ve noticed the following:
- If a table name is unique across all schemas, the schema prefix is not shown.
- If multiple schemas have the same table name, the semantic model displays the schema prefix to disambiguate.

This makes sense.

Issue:

I have a Fabric notebook that performs schema swaps; moving tables from one schema to another by dropping and recreating them. However, I've observed inconsistent behavior in how tables are referenced after the swap:
- Sometimes, the schema prefix appears in the semantic model even though the table name is unique.
- Other times, the prefix doesn’t appear as expected.

Is there a way to force schema-qualified names consistently in the semantic model? Is this behavior due to metadata caching or some other underlying logic?

Any insights or workarounds would be appreciated!

Thanks in advance!