Forum Discussion
Suddenly Fabric is complaining about wrong datatype (date) from lakehouse to warehouse
- 1 year ago
Hi! I did raise a ticket and got this answer (in March 2025) after a couple of back-and-forths:
"We would like to inform you that we have received an update from our product team. The issue you reported has been identified as a bug in the backend, and our product team is currently working on the fix. In the meantime, they have provided a workaround: export the PQT file of the failed dataflow, create a new dataflow, import the template, and reset the output destinations."
I have excatly the same issue.
Broke like a week ago and I fixed it by recreating the entire DataFlow Gen2.
Now suddently I it breaks down again on all tables containing a date. Other tables works fine.
So frustrating
- nioj2S1 year ago
Advocate I
Yeah, noticed that deleting the dataflow and recreating it worked. Could at least use the "Export template" as a base, but still annoying having to redo all the data destinations and mappings.
Also had another date related issue yesterday, where date filtering suddenly stopped working. Just had to remove that step in the power query steps and redo it exactly the same, then it started working. And my colleague had issues with locales suddenly stopped working, so he had to redo those steps. Fabric is introducing way too many new bugs at the moment...