Forum Discussion
Lakehouse Table Created with Columns Only, but No Rows (0 Records Loaded)
- 1 year ago
Hi Aala_Ali ,
Yep, I’ve seen this happen a few times — especially with Dataflow Gen2 in Fabric. If your table is created but no rows are loaded, even though the preview shows data, here are a few things to check:
Final step output: Make sure the last step in your query is actually returning a table (not a record or list). Sometimes a small transformation can change the output type without warning.
Column mapping: Even if it looks correct, try switching from “Dynamic” to “Manual” mapping and re-map the columns — this sometimes forces the data to persist properly.
Data types: Double-check that none of the columns have unsupported or null-only types — Fabric can silently skip rows if it can’t serialize the data.
Try a smaller dataset: Filter down to just a few rows and test again — this can help isolate whether it’s a data issue or a pipeline issue.
Also, there have been a few caching quirks with DFG2 — clearing browser cache or using a different browser sometimes helps during testing.
Let me know if you want help checking the query output or mapping setup — happy to take a look!
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
Hi Aala_Ali ,
Yep, I’ve seen this happen a few times — especially with Dataflow Gen2 in Fabric. If your table is created but no rows are loaded, even though the preview shows data, here are a few things to check:
Final step output: Make sure the last step in your query is actually returning a table (not a record or list). Sometimes a small transformation can change the output type without warning.
Column mapping: Even if it looks correct, try switching from “Dynamic” to “Manual” mapping and re-map the columns — this sometimes forces the data to persist properly.
Data types: Double-check that none of the columns have unsupported or null-only types — Fabric can silently skip rows if it can’t serialize the data.
Try a smaller dataset: Filter down to just a few rows and test again — this can help isolate whether it’s a data issue or a pipeline issue.
Also, there have been a few caching quirks with DFG2 — clearing browser cache or using a different browser sometimes helps during testing.
Let me know if you want help checking the query output or mapping setup — happy to take a look!
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.