2 weeks ago
Hello everyone!
We noticed a very unusual behavior after upgrading some of our machines to Windows 11 24H2.
The expression FormatDate(Today(),"MMM") is returning "Sept" instead of the expected "Sep".
Useful Windows setting:
Edition: Windows 11 Enterprise
Version: 24H2
OS Build: 26100.9168
Windows Feature Experience Pack 1000.26100.344.0
Country or region: Belgium
Regional format: English (Belgium)
CultureInfo.CurrentCulture.Name = en-BE
CultureInfo.CurrentUICulture.Name = en-US
Thanks in advance.
Answered! Go to Answer.
2 weeks ago
As you probably determined, this is an intentional change that isn't caused by Blue Prism. It would affect any application using .NET to generate the abbreviation of months. Lots of people have gone through this outside of Blue Prism. Here is an example:
Why did Windows 11 24H2 update change English (New Zealand) AbbreviatedMonthName (MMM) for September from Sep to Sept? - Microsoft Q&A
In the very last reply on that thread, the person explains that it was an intentional change by Microsoft to align with standardized abbreviations. This is normal for Microsoft. They tend to take much longer than any other technology stack to adapt to some global/industry standard.
I would suggest embracing the new spelling. If it has broken any automations, then of course you can create your own object action to return the 'Sep' spelling, or specific automations reliant on it could take the first 3 letters or have a choice stage of its own to return Sep when the month is 9 or something like that.
2 weeks ago
As you probably determined, this is an intentional change that isn't caused by Blue Prism. It would affect any application using .NET to generate the abbreviation of months. Lots of people have gone through this outside of Blue Prism. Here is an example:
Why did Windows 11 24H2 update change English (New Zealand) AbbreviatedMonthName (MMM) for September from Sep to Sept? - Microsoft Q&A
In the very last reply on that thread, the person explains that it was an intentional change by Microsoft to align with standardized abbreviations. This is normal for Microsoft. They tend to take much longer than any other technology stack to adapt to some global/industry standard.
I would suggest embracing the new spelling. If it has broken any automations, then of course you can create your own object action to return the 'Sep' spelling, or specific automations reliant on it could take the first 3 letters or have a choice stage of its own to return Sep when the month is 9 or something like that.
2 weeks ago
Monday
How very strange. I've been treating "MMM" as synonymous with a strict 3-character width for decades - who knew that Apple did it different and a consortium of OS builders would change to align with them!
Tuesday
Following up/closing the loop on this thread; one of my colleagues just published this Knowledge Base article yesterday with additional information about this change introduced by Microsoft and how it can affect Blue Prism automations:
Why does FormatDate function in BPE return different month abbreviations on Windows 11 24H2?