Known issue: .NET parses ShortDate expecting 4 digits in the year (2022, not 22)
KB003700
PRODUCTIssue
When using the Out of Office feature and have configured the system to forward your tasks to another user, tasks are not forwarded.
Reason
Because of the way .NET handles date and time formatting while parsing, if the year of the operating system's short date consists of only two digits (yy instead of yyyy), the .NET call returns the date in a way that K2 reads as a null value instead of a valid date.
For example:
If the date is the 9th of November 2022, and the operating system shows this in the short date format as 09/11/22, K2 reads the .NET call return value as 09/11/0022, which is not valid for the system.
Resolution
Some of the regions in Microsoft Windows have the default short date set as dd/mm/yy, this causes the issue described in this article. To resolve the issue, an administrator must set the short date to dd/mm/yyyy on all K2 servers in the environment. For example:
| Incorrect short date | 09/11/22 |
| Correct short date | 09/11/2022 |
To do this, follow these steps:
- In Windows, click Start and search for Region Settings.
- On the Region tab, click Change data formats under the Regional format data section.
- Change the Short date to the yyyy format.
- When you go back you will see the Regional format data set to yyyy.
This causes the system to parse the date correctly as the full year is present.
