Unexpected datetime >= evaluation by Alteryx

[Diederik_vanderharst]

We are using a generate rows to create a month scaffold between this month (including this month) and the last month of the next year, august 2024 up and including to december 2025.

NB: Today is 2024-08-21
When the following config is used somehow the Condition Expression is met until 2024-09-(21) but the row for 2024-08-21 is not generated, which we would expect. YearMonth(2024-08-21) >= 2024-08-21 (DatetimeNow()) = TRUE is it not?

I'm puzzled, as is my colleague. We can get to the desired outcome, but we wonder what part of the Alteryx Logic we are missing that results in this behaviour.

Those who suspect the addition of 6 hours might complicate things, here's the outcome of a simplified effort:

Love to hear your answers!

[ChrisTX · Accepted solution]

Use the ToDate function in your Condition Expression

In your current Condition Expression you're comparing a Date to a DateTime. My guess is that 

the Date value 2024-08-21 is NOT >= a DateTime value like 2024-08-21 10:42:08

 

Chris

[Raj]

@Diederik_vanderharst 
find the workflow attached
mark done if solved.

[Diederik_vanderharst]

Thanks @ChrisTX and @Raj for contributing. todate() fixed the issue and also explained the behaviour.