- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Lakehouse ADLSGen2 Shortcut Delta/Parquet files not recognized as tables
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- jmdublu on: ISSUE: Series Value "All" in Legend Adversely Affe...
- jozseftuska on: Azure SQL DB bug in identifying the primary key fo...
- v-jtian-msft on: Slicer values not passed as bind parameter values ...
- v-jtian-msft on: Power App Patch with Success or Error message
- v-jtian-msft on: Table Filter does not work based on slicer selecti...
- v-jtian-msft on: Full Measure name not shown in Conditional Format
- v-xiaoyan-msft on: Improve Accessibility in Power BI Export to PDF.
- v-xiaoyan-msft on: Composite model. Measures do not IGNORE format str...
- Muratmet123 on: Making a custom theme using a JSON file
- v-xiaoyan-msft on: Refresh error
- New 7,842
- Needs Info 3,500
- Investigating 3,476
- Accepted 2,077
- Declined 38
- Delivered 3,945
-
Reports
10,051 -
Dashboards
4,052 -
Data Modeling
4,050 -
Gateways
2,091 -
Report Server
2,088 -
APIS and Embedding
1,935 -
Custom Visuals
1,748 -
Content Packs
516 -
Mobile
352 -
Need Help
11 -
Show and Tell
3 -
General Comment
2 -
Tips and Tricks
1 -
Power BI Desktop
1
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