Lakehouse ADLSGen2 Shortcut Delta/Parquet files not recognized as tables

[Axelplore]

Hi,

I was able to create a shortcut from Lakehouse to ADLSGen2 delta parquet files with the guidance of Create an Azure Data Lake Storage Gen2 shortcut - Microsoft Fabric | Microsoft Learn and Wait! We can use Databricks data with Microsoft Fabric??? (youtube.com) But unfortunately there is following error message if I try to do the tables shortcut: "Unable to identify these objects as tables. To keep these objects in the lakehouse, move them to Files. Shortcuts can’t be moved directly, but you can recreate them in Files and then delete them here."

The lakehouse doesn't identifie the objects as tables. On the other hand the data from the parquet files can be accessed via notebook and pyspark. So actually the data is available but can't be viewed in the Lakehouse respectively won't be identified as table objects.

I also tested this issue with CSV files. And there is the same error message.

Are there some bugs within the shortcut function? Have you encoutered same issues?

[v-xiaoyan-msft]

Hi @Axelplore,

Based on the above information, this issue is complex which may need to collect log files for further troubleshooting. Since community support engineers don't have that access, I would suggest opening a Support Ticket. If you are a Power BI Pro or Fabric licensee, you can create a support ticket for free and a dedicated Microsoft engineer will come to solve the problem for you. 
It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.

The link of Power BI Support: Support | Microsoft Power BI

For how to create a support ticket, please refer to How to create a support ticket in Power BI - Microsoft Power BI Community

Best Regards,
Community Support Team _ Caitlyn

[Alflpedersen]

I have Got the same issue

[Axelplore]

I am still working on that issue with the MS Support. I will let you know when I got any news.

[Axelplore]

After investigating the issue with the support, the reason this is happening is because the shortcut name has the "-" (i.e. hyphen) character, which is not a supported character for table name, resulting in the table not being identified correctly.

Still the question is why hyphen characters causes the errors. The support product team has identified the issue as a Bug. Currently, there is no roadmap available for this issue.

The problem is, we are testing the shortcut function for the link to databricks and it is not an option to manipulate the generated UID (tablename) with hyphen characters from databricks.

So currently the shortcut function is not an option for us to link the data with Fabric.

Kind regards

axelplore