Shortcut on another lakehouse

[DwijaKeerthi]

I have a lakehouse1 with Table1, I created a shortcut on Lakehouse2 for my requirement. 

On Lakehouse1 if I drop the table, shortcut is couldn't load and it is expected. 

If I load table1 back on lakeshouse1 with no change in schema, still my shortcut is not recognizing. In order make the shortcut work, I have to do these steps:

Go to Lakehouse2-->Manage shortcut-->Edit Properties-->TargetPath-->Select the same table1(on lakehouse1) again on "update shortcut" pop-up and click on next and update; then my shortcut works as usual..

Is there a way that I can remove these steps. Because on my lakehouse1 I have to drop and create always. 
But I cannot ask other fellow members who are using this table with a shortcut to follow these steps.

[v-pnaroju-msft]

Hi DwijaKeerthi,

We are following up to see if what we shared solved your issue. If you need more support, please reach out to the Microsoft Fabric community.

Thank you.

[v-pnaroju-msft]

Thankyou, @cengizhanarslan for your response.

Hi DwijaKeerthi,

We appreciate your inquiry through the Microsoft Fabric Community Forum.

We would like to inquire whether have you got the chance to check the solution provided by @cengizhanarslan  to resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.

Thank you.

[cengizhanarslan · Accepted solution]

A Lakehouse shortcut is not a live pointer that rebinds itself when the source table is dropped and recreated. Fabric treats it as a new table with a new internal object identity. The shortcut in Lakehouse2 still points to the old object ID, which no longer exists. There is currently no auto-rebind, no “follow by name", no background refresh that repairs shortcuts.

If you depend on shortcuts, the safest pattern is:

• Create the table once

• Then use:

  • INSERT OVERWRITE

  • MERGE

  • TRUNCATE + INSERT

  • Overwrite mode in Spark

As long as the table object itself is preserved, the shortcut will never break.