Forum Discussion
DFGen2 Unable to create Destination table in Lakehouse
1: First time trying this out
Memorable MemberMarcusA btw, and I should have mentioned this before, since you are trying to extract from an on-prem DB, have you tried the 2 dataflow chained workaround? Here, Microsoft briefly explains:
This workaround solved the 'Something went wrong' error in the data destination dialog for me, as well as the other errors that would pop up at refresh time (after you publish).
Have tried the workaround, did not work for us.
- Element115
We need more details MarcusA to help you better.
Can you see data coming in in the first DF?
Did you Enable staging on the query in the first DF and disabled it on the query in the second DF?
Did you set a data destination on the query in the second DF BUT NOT on the query in the first DF?
I've tried the workaround mentioned and it didn't work.
- Element115
Screenshot, code and details please.
Thanks for your enquiry. My dataflow Gen2 were working well since I've created them last week. It's only from this morning they started failing to refresh. I detached the destinations and they were working well. But couldn't reconnect with the destination lakehouse again.
I had followed the workaround by creatng a staging dataflow and then connect my dataflow gen2 taking data from that staging dataflow. It still didn't work.
