Suddenly dataflow refresh error SqlDateTime overflow

[Alex_Rajkov]

Since this morning dataflow throws the following error while refreshing from MS NAV 13 via ODATA connection.

Invalid date,NAV ODATA TEST,Fehler,Verkaufsgutschriftszeile,12/08/2019 16:23:58,12/08/2019 16:24:28,Fehler,Error: An internal error occurred... RootActivityId = 415c20ec-6fd7-40e6-b6e3-0f8521044913.Param1 = SqlDateTime overflow. Must be between 1/1/1753 12:00:00 AM and 12/31/9999 11:59:59 PM. Request ID: 95a6922e-4408-56f7-17ec-82af235cc283.

No changes being made in the simple PQ script. Its just get the columns and define the column datatype.
Already checked the MS NAV database system time. Everything is just fine there. 

The dataflow worked just fine til last week.

In the dataflow options I (had to) change the region from Germany to English (United States). But tested reversing back to Germany also. No success.

The same refresh works just fine via PBI Desktop..

Help needed.

[Alex_Rajkov]

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

[marcusearly]

@Alex_Rajkov 

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.

[Alex_Rajkov]

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...

[marcusearly]

@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.

[Alex_Rajkov]

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.

[marcusearly]

@Alex_Rajkov  did turning off the enhanced compute engine solve your issue?

[Alex_Rajkov]

Yes, it did.

[marcusearly]

I believe we have turned on the new compute engine. At a global organization so I cannot turn off unfortunately.

[v-shex-msft]

Hi @Alex_Rajkov ,

According to error message, It seems like you have inputted wrong datetime parameter.
Current power bi not recognize datetime values who greater than 12/31/9999 or less than 1/1/1753. Please use valid datetime value to instead current one.

Regards,

Xiaoxin Sheng

[Alex_Rajkov]

Hi Xiaoxing,

according to your response you didn't read my post.

You simply stated the error message.... 😞

KR
Alex

---

@v-shex-msft wrote:

Hi @Alex_Rajkov ,

According to error message, It seems like you have inputted wrong datetime parameter.
Current power bi not recognize datetime values who greater than 12/31/9999 or less than 1/1/1753. Please use valid datetime value to instead current one.

Regards,

Xiaoxin Sheng