Community forum

Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


Guido Worch
2017-06-19T14:48:33Z
After upgrading from 8.25? to 8.27, my weekday conditions seem to not work like before.
We used to have
{DATE(WeekDayNumber|Monday)}
and it would return 1 for Monday and up until 7 for Sunday.

Now it seems it always returns the number of the weekday given as StartOfTheWeek.

So the above is now always returning 1, and {DATE(WeekDayNumber|Sundday)} is always 7.

I had to change my weekday conditions to {DATEFORMAT(dddd)} and query the returned string,
but that's not really good, as it is locale specific.

No one else having the same problem?

Thanks
Guido
Sponsor
Forum information
Support
2017-06-19T16:05:19Z
It still returns 1 for Monday and 7 for Sunday. Maybe your regional settings has changed?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Guido Worch
2017-06-20T06:10:54Z
Thanks Henrik
Just to make sure I got that right.
As today is Tuesday, it is supposed to return 2, right:
{DATE(WeekDayNumber|Monday)}

in variables preview this returns 1 here.
I don't see how a regional setting would change that value, given we specify the first day of the week.

We did upgrade VC and did patch the 2012R2 server then this behaviour changed.
Support
2017-06-20T09:18:32Z
Hi,

no, the number it returns depends on the incoming day - not the current day. It just parses "Monday" or "Tuesday". We will add a simple:

{DATE(WeekDayNumber)}

And that will return the current day number of week.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Guido Worch
2017-06-20T10:13:30Z
{DATE(WeekDayNumber)}
is giving me Error in argument ...?
Support
2017-06-20T11:11:36Z
Originally Posted by: Guido Worch 

{DATE(WeekDayNumber)}
is giving me Error in argument ...?



We will add this for the next build. Currently not available.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Guido Worch
2017-06-20T11:28:27Z
Very good, thank you.
That's gonna solve my problem.

I still wonder though, my tasks used be properly executed on the required weekday using
{DATE(WeekDayNumber|Monday)}
and querying the condition for Monday 1, Tuesday 2 and Friday 5 until we updated in May.

Since no one else is having the same problem it must be something on our end.
Quite strange.
Support
2017-06-22T08:11:22Z
Originally Posted by: Guido Worch 

Very good, thank you.
That's gonna solve my problem.

I still wonder though, my tasks used be properly executed on the required weekday using
{DATE(WeekDayNumber|Monday)}
and querying the condition for Monday 1, Tuesday 2 and Friday 5 until we updated in May.

Since no one else is having the same problem it must be something on our end.
Quite strange.



Yes, we do not recall any change here.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
nhkab
2017-06-27T14:00:14Z
We are also experiencing this problem with our upgrade to 8.2.7

The Variable value {DATE(WeekDayNumber|Monday)} output is equivalent to the day of the week that is placed in the string (Monday/Tuesday/etc) and not the actual day of the week it is.

This has broken all of our conditional statements.
Support
2017-06-29T08:48:57Z
Scroll to Top