The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
We are currently in the process of planning and implementing a small scale PoC to test out Fabric's capabilities.
One of the larger issues that we have recently run into has left us very confused. We're using Dataflow Gen2 to fetch data from Snowflake into our new lakehouse and our old PowerQuery queries seem to be working just fine (the preview data looks correct, no errors etc). After we run our dataflow we can see the tables appear in our lakehouse - but we are missing roughly half, sometimes more of the columns. Rerunning the dataflow does nothing to fix this, neither does removing and readding the queries in it.
What could cause this?
Some notes:
Try changing the data type of the columns. I was facing the same issue, but noticed that missing column didn't have a type, so I just clicked "detect data type" when editing the dataflow gen2 and that worked for me! Let me know if it does for you.
This isn't going to help much, but I have the same item happen to me. I've also noticed that I have 2-4 columns and the last column ends up being a "measure". My only work around was to always add the dataflow by "Getting Data" when viewing the Lakehouse, and selecting the Dataflow Gen2 there.
I am experiencing the same problem with data flow gen2, specifically the key column does not show up in the mapping section of add/ edit data destination to lakehouse. does not show up in the lakehouse either.
I am also facing same kind of issue "Missing all Primary key columns"
I think this might be a different issue to the one being described here. Could you please create a new thread with mroe details about your scenario and if you could share some repro steps for us to replicate this issue on our end that would be really helpful
I'd start by checking the settings of the output destination to make sure that all columns were mapped as loading to the destination table. If there's in fact a mapping of the columns and yet you don't see data being loaded for those columns, and there should be data loading, please reach out to our customer support team.