Creating OneLake shortcuts: "Unidentified" issue happens randomly

[frithjof_v]

I have created two lakehouses, and shortcut between them.

Some times, the shortcuts show as "Unidentified" and it says I need to move the contents to the File section:

In another lakehouse, the shortcut works fine:

I didn't do any changes between the time when I created the two shortcuts. 

Seems like a bug.

It happens some times both when I create the shortcut through the GUI, or through semantic-link-labs.

Anyone found a way to avoid this Unidentified issue?

Thanks!

[FabianSchut · Accepted solution]

I get these "Unidentified" issues also on random moments in time. Most of the time, these are solved after waiting a few minutes and by closing and re-opening the lakehouse. Do you need to re-add the shortcuts before it is working or does it also resolves itself by waiting?

[Anonymous]

Hi @frithjof_v ,

Can you please share some more detail information about these operations? They should help us clarify your scenario and test to troubleshoot.

Regards,

Xiaoxin Sheng

[frithjof_v]

In Lakehouse A, I have a managed delta table in the Table section.

In Lakehouse B, I create a shortcut in the Table section. The target path of the shortcut is the managed delta table in Lakehouse A's Table section.

Sometimes it works, other times it shows as Unidentified.

I try clicking all the refresh buttons I can find, and wait for several minutes, but the shortcut still shows as Unidentified and it says I need to move the contents to the File section.

If I delete the Unidentified shortcut, and return 10 minutes later and try to create the same shortcut again, then sometimes it will work fine.

It seems random why it sometimes shows as Unidentified when I create a shortcut, and sometimes it works fine creating the same shortcut.

To try to recreate the issue, I suggest creating 10-20 shortcuts between Lakehouse tables in different workspaces, and check if some of them show as Unidentified.

[Anonymous]

HI @frithjof_v,

Any update on this? Did this issue still appear regularly on you side? If that is the case, you can also consider report to dev team and ask them help you find the root causing about this issue to fix it.

Regards,

Xiaoxin Sheng

[Anonymous]

HI @frithjof_v,

I think they may related to the multiple level of shortcut reference, each level of them will spend time to load data and revengers correspond contents.(AFAIK, shortcut only loading data without data movement)
If some of them not correctly finish loading, they may affect the following operations and show the Unidentified.
This scenario will appear more frencey when you used a lot of shortcuts that design with multiple level reference.

Regards,

Xiaoxin Sheng

[FabianSchut · Accepted solution]

I get these "Unidentified" issues also on random moments in time. Most of the time, these are solved after waiting a few minutes and by closing and re-opening the lakehouse. Do you need to re-add the shortcuts before it is working or does it also resolves itself by waiting?

[frithjof_v]

Thanks for sharing! I only waited a couple of minutes. I tried clicking all possible refresh buttons. It didn't solve itself within those couple of minutes. Perhaps if I waited longer, it would solve itself? But it should not be necessary to wait so long time.

I just deleted the shortcut after some minutes because it still showed as Unidentified.

When I came back perhaps 10 minutes later, I was able to create a new shortcut successfully, using the same table.

It seems random: sometimes it works, sometimes it doesn't.

[FabianSchut · Accepted solution]

I agree that it should not be necessary to wait so lang. However, it does work for me most of the times. I've never timed the interval between Unidentified and the working shortcut, but more than a few minutes is possible. This still needs to be resolved, this feels like a bug to me too.

[lbendlin]

If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .