Forum Discussion
Creating a Table Shortcut in Fabric from a Partitioned Delta Table
- 2 years ago
Interesting. I've never tried creating shortcuts in a schema enabled Lakehouse myself. Are you sure you want to use the schema enabled Lakehouse? It's only a preview feature...
Is this part of the documentation relevant for your case (did you try the schemas shortcut option)? https://learn.microsoft.com/en-us/fabric/data-engineering/lakehouse-schemas#bring-multiple-tables-with-schema-shortcut
Are you creating the shortcut in the Tables or Files directory of the Lakehouse?
Please note if you create the shortcut in Files and then choose Load to Table, your Table will not be connected to the data source. The Load to Table creates a point-in-time copy of your data at the time you click the Load to Table button.
If you want a Table which is connected to the original data source via a shortcut, the best option is to create the shortcut directly in the Tables section of the Lakehouse.
frithjof_v Thank you for your reply. I have tried both. I created two testing Lakehouses, one with Schemas enabled and one normal one. In the normal one, I can create shortcuts from these partitioned tables without error. From the Schema Lakehouse, I get this "Unable to load table view" both when trying to use a shortcut and when trying to use Load to Table.
- frithjof_v2 years agoCommunity Champion
Interesting. I've never tried creating shortcuts in a schema enabled Lakehouse myself. Are you sure you want to use the schema enabled Lakehouse? It's only a preview feature...
Is this part of the documentation relevant for your case (did you try the schemas shortcut option)? https://learn.microsoft.com/en-us/fabric/data-engineering/lakehouse-schemas#bring-multiple-tables-with-schema-shortcut
- jrauenbuehler2 years agoRegular Visitor
I also tried the schema shortcut but it didn't work either unfortunately.
- jrauenbuehler2 years agoRegular Visitor
Not planning to use the schema enabled lakehouse anymore. I found a workaround for what I need so I can just resolve this issue. For my work-around, I wrote a CREATE SCHEMA script in the warehouse and created views within the schema I wanted them. Works fine for now. I wanted to have the tables in the schemas as well but it's fine for now.