Transient Error message when loading lakehouse with a dataflow gen2

[BernatAgulloAnt]

Hello,

I copied a PQ code into a Dataflow Gen2 and it worked fine. It loaded the lakehouse and even connected to the sqlendpoint through SSMS. So far so good.

Then I tried reading from that sqlendpoint from a powerapp like a SQL  Server datasource, and that did not complete (kept spinning for a long while until I gave up)

When I entered the lakehouse I saw the following error

"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 dataflow reads from an Azure Blob Storage all the json files returned from the API on the last extraction.

Yes, there was a successful refresh of the dataflow

upon clicking refresh though the issue seems to resolve itself

that happened a minute or so later

[Anonymous]

Hi  @BernatAgulloAnt 

Lakehouses are composed of two top level folders: the Tables folder and the Files folder. The Tables folder represents the managed portion of the lakehouse, while the Files folder is the unmanaged portion of the lakehouse. In the Tables folder, you can only create shortcuts at the top level. Shortcuts aren't supported in other subdirectories of the Tables folder. If the target of the shortcut contains data in the Delta\Parquet format, the lakehouse automatically synchronizes the metadata and recognizes the folder as a table. In the Files folder, there are no restrictions on where you can create shortcuts. You can create them at any level of the folder hierarchy. Table discovery doesn't happen in the Files folder.

We could see in your picture,please keep this in mind those are folders for different tables. If so, Lakehouse cannot recognize those as 'a' table as there are multiple table folders.This is a temporary issue, as it is still a preview feature and is being improved.

https://learn.microsoft.com/en-us/fabric/onelake/onelake-shortcuts#lakehouse 

Best Regards,
Community Support Team _ Ailsa Tao

[BernatAgulloAnt]

if you read my message until the end, you will see that the issue solved itself.

I just posted it here because the PM team asked me to do so. 

is an error that should not display