Unable to see existing lakehouse tables within schemas in Dataflow Gen2

[jackcapel]

Hi I am experiencing odd behaviour in my fabric dataflows. When I try to select a destination I can connect to my lakehouse but the list of tables is empty. If i create a new table in the default dbo schema this is visible in the list. All of my other tables are in schemas in the lakehouse.

I'm sure this worked before and I was able to select from any of the existing tables regardless of the schema they are in.

you can see the insight_lakehouse item is empty where in reality there are dozens of tables.

Thanks in advance for your help,

Jack

[Shahid12523]

Right now Dataflow Gen2 only lists tables in the default dbo schema when you pick a Lakehouse destination.

Tables stored in custom schemas don’t show up in the selector (even though they exist in the Lakehouse).

Workarounds:

Create the destination table in dbo schema if you need it selectable in Dataflow Gen2.

Or load data into a new dbo table and later move/organize it with SQL in the Lakehouse.

For existing tables in custom schemas → access them via SQL endpoint instead of through the Dataflow UI.

This looks like a Fabric product limitation/bug (it did work earlier, but recent updates restrict visibility to dbo).

Best next step: raise a support ticket or post in the Fabric Community so Microsoft can confirm if it’s a regression.

[v-sdhruv]

Hi @jackcapel ,

I hope were able to temporarily fix the issue.
Thanks Pallavi for your inputs.
You can check the known issue here- Microsoft Fabric Known Issues
or can even raise a support ticket to resolve your query - Microsoft Fabric service status

Hope this helps!

[pallavi_r]

Hi @jackcapel 

Seems that's a limitation right now in dataflow gen 2. Even I have tried this multiple time, it did not work. if we try to point to existing 'non-dbo schema' tables, it does not list out the tables from non-dbo schema, and also we cannot create a new table with different schema while giving the destination.

Workaround would be to load it to dbo, then separate pipeline to put it in right schema using notebook or sql.

Or else you can directy use notebook instead of dataflow gen 2.

If this post helps, please accept this as a solution. Appreciate your kudos.

Thanks,
Pallavi

[jackcapel]

Hi Pallavi, thanks for your response. This is exactly how i have had to work around the issue. The table exports to dbo then a notebook runs to change the schema.

[v-sdhruv]

Hi @jackcapel ,

Try to refresh and see if are getting the tables.
Additionally, check out this similsr post which might help-

Solved: Lakehouse table schema not updating at dataflow re... - Microsoft Fabric Community

Hope this helps!