Skip to main content
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Did you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now

Banzai

Dataflow refresh error Date/Datetime

Submitted by Advocate II on ‎06-14-2021 02:13 AM

Started getting this error on an old dataflow as of 14-Jun-2021. No changes made.

 

Error: Expression.Error: We cannot apply operator < to types Date and DateTime.

Operator = <

Left = 5/1/2020 12:00:00 AM

Right = 9/30/2020 11:59:59 PM

 

 

Status: New
See more ideas labeled with:
40 Comments (40 New)
Comments
v-chuncz-msft
Community Support
Community Support
‎07-01-2021 02:17 AM

@Banzai 

 

The fix is deployed. You may check it again.

Banzai
Advocate II
Advocate II
‎07-01-2021 07:40 PM

Yep, seems to be working again with the Enhanced Compute Engine. Turning it on cut down the processing time to ⅓ with the heavier transformations. Thanks.

EMaguire
Frequent Visitor
‎07-02-2021 07:16 AM

I've also re-enabled the Enhance Compute Engine on some of the dataflows that were affected and it seems to be working successfully again. Thanks!

steveplatz2
Frequent Visitor
‎07-02-2021 07:46 AM

The issue also appears to be resolved for me. The super simple repro I sent to Microsoft is now able to refresh with enhanced compute turned on without issue. 

mikesmith_bp
Frequent Visitor
‎07-06-2021 05:34 AM

It looks like this issue is now behind us.

 

But an even bigger issue is why does Microsoft not acknowledge theses issues? I've had several of these bugs over the past 2 years which have crippled my dataflows.  It would be so much easier for me to commucate with my users if I had an official statement from Microsoft.  Instead Microsoft clains Power BI is running normal.

EMaguire
Frequent Visitor
‎07-12-2021 09:09 AM

Hi - I seem to have a recurrence of this same issue, since Saturday 10th July. Is this affecting anyone else again?

john_ach
Frequent Visitor
‎07-12-2021 09:13 AM

Yes, I seem to be getting the same (or very similar) error again. I've had to reintroduce the DateTime.Date( ) casting on comparisons again.

 

I'm also getting the error below which seems to be new, though I couldn't guarantee that the source data hasn't changed - any suggestions?

Expression.Error: We cannot convert the value #datetime(2019 5 11 23 59 59.9999999) to type Date

Banzai
Advocate II
Advocate II
‎07-12-2021 09:31 AM

Same here. As of 12-Jul-2021.

 

Oh, for Pete's sake! 😞

 

Error: Expression.Error: We cannot apply operator < to types Date and DateTime.

Operator = <

Left = 1/1/2020 12:00:00 AM

Right = 6/30/2021 11:59:59 PM

EMaguire
Frequent Visitor
‎07-12-2021 09:48 AM

Thanks @Banzai and @john_ach for confirming it's not just me.

 

I've 'fixed' the problem again by disabling the enhanced compute 😥. But this is so frustrating and tedious!

Anonymous
Not applicable
‎07-13-2021 12:07 AM

We also had the same issue re-appear and were in contact with Microsoft about it. They helped us by changing some settings for our capacity. Their comment: 

 

The issue was caused by the previous fix you had not being deployed in the latest change that happened over this past weekend.  That then caused you to see the same issue because the fix was no longer there. 

We were able to mitigate the issue by placing your capacity on a previous version where the fix is at. You had to revert to Premium Gen 1 since Gen 2 currently does not have that same ability to go back a previous version.  You can now refresh as expected.

The underlying issue should be resolved over this upcoming weekend when they will push your previous fix to the next Service change. 

Idea Statuses