Forum Discussion
Suddenly dataflow refresh error SqlDateTime overflow
After further tests, I assume the problem seems to be that there is some kind of query folding.
The problematic query doesn't contains any datetime statements. Just renaming of column names and changing the column type.
But the MS NAV 13 ODATA query contains a filter on the posting date. Posting_Date=FILTER(01.01.18..)
The filter works just fine in NAV and gives me the filtered table. Also in PBI Desktop I get the result.
Just PBI dataflow has an issue - and only with the beginning of this week.
1. How are we supposed to use dataflows, if the behavior changes without beeing informed of changes under the hood?
2. Why are the current bugs not solved?
a) A german user has to change the locale in dataflow to english, for it to work properly.
b) There is the date / datetime issue. Every time a column type is changed to just date and the entity is linked to another dataflow or loaded into PBI desktop the column type is datetime again...
Please solve these minor issues.
KR
Alex
I have the same issue happening. Suddenly getting this on a dataflow that has been working for months:
Error: An internal error occurred... RootActivityId = 710a9c86-c5ea-4a6d-be0d-2ff48508cbfa.Param1 = SqlDateTime overflow. Must be between 1/1/1753 12:00:00 AM and 12/31/9999 11:59:59 PM. Request ID: 0ff1c41f-fc08-454a-a2c0-95aeae3006a2.
If I convert DateTime columns to Text, it refreshes without issue. Something was messed up this last week in the Time format. It doesnt happen in the desktop model.
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.
