Forum Discussion
Suddenly dataflow refresh error SqlDateTime overflow
Not good, but good to hear I am not the only one.
I have a call with MS Support tomorrow and will post again if I have a solution.
Right now I fixed it by inserting replace value #date(1,1,1) with null for all date columns...
Alex_Rajkov I was able to get past this in the dataflow today. I had a few date/time fields that had "0217" rather than "2017". This was never really a problem before and have been in the dataset for months. I corrected these prior to converting to date/time and the dataflow now refreshes. I wonder in the past if this would have come back as "0217" as the year... whatever change they put in has this now appearing as "217" which triggers the error.
I am curious, did you also change to the new dataflow enhanced compute engine?
Even after fixing that new problem, I ran into more problems with dataflows.
refresh of dependent dataflows not refreshing with the source dataflow. Refresh runs forever, dataflow wouldn’t open to edit, other never seen before error messages...
I deactivated it today and so far so good.
I believe we have turned on the new compute engine. At a global organization so I cannot turn off unfortunately.
Alex_Rajkov did turning off the enhanced compute engine solve your issue?
Yes, it did.