cancel
Showing results for 
Search instead for 
Did you mean: 

Dataflow Refresh Problem - We cannot convert the value #datetime() to type Date- URGENT!

Since Monday our dataflows stopped updating

 

The error that is given is the following: “Error: Expression.Error: We cannot convert the value #datetime(2019 9 26 0 0 0) to type Date. .. RootActivityId = da928912-31f6-40a6-994c-761c55104956.Param1 = Expression.Error: We cannot convert the value #datetime(2019 9 26 0 0 0) to type Date. Request ID: a033c9df-0c02-7ccf-df39-c48a1c29335c.

 

 And it happens in all 3 workspaces (dev-test=prod and with different tables and different dates!)

 

We also notice that the datetime function in the error message is missing commas. We haven't made any changes in the code and are not explicitly doing any datetime to date conversion... 

 

This is a critical problem for us because the whole organization is now dealing with 2 days old data. Please advice!

Status: New
Comments
Jaap_Olsthoorn
Post Patron

Experiencing the same issue here!

InsightBob
Frequent Visitor

Did you get resolved?

olgaia
Frequent Visitor

Talking to a Microsoft engineer now and will write here if we have a resolution!

InsightBob
Frequent Visitor

Ditto!

Can i ask, is your problem happening where you have linked entities in your dataflow?

olgaia
Frequent Visitor

Yeap, linked entities and premium capacity

InsightBob
Frequent Visitor

Thanks for sharing! Sounds exactly the same as our issue

judgejebber
Regular Visitor

Found another possible workaround which seems to be doing the trick for us (until resolved by MS).
Add a “Remove Errors” step on the date column prior to the step that errors out.

Not causing  any data loss and it looks like its working for us. Hopefully that helps someone else out!

v-chuncz-msft
Community Support

@olgaia 

 

Thanks for your update. We understand that the issue may be urgent and you have created a support ticket. Hopefully, it could be resolved soon and it would be great if you could share the solution to help more users.

InsightBob
Frequent Visitor

Switching off enhanced compute engine for affected dataflows also resolves - that may be root cause

steveplatz2
Regular Visitor

Switching off enhanced compute also worked for me.