Hello everyone,

today we observed a pretty strange behavior of date columns in the new SharePoint lists (= MS Lists layout) in all of our customer tenants. The tenants are in time zone “W. Europe Standard Time” (= UTC + 1) (this is also the setting in the “Regional Settings” of each SharePoint site).

When we select a date value before 01.01.1980 and the month is one-digit “1 – 9” (January – September), it shows the date correctly in the EditForm, but in the SharePoint list itself it is displayed in UTC (which means the date is shifted 1 day to our selected date in the EditForm):

However, this only happens when the month has exactly one digit. If it has two digits (10, 11, 12 = October, November, December), the displayed date values in the EditForm and in the SharePoint list are identical, no matter which year was selected:

Even more strange is that the problem with the date differences does not occur when you select a date with a one-digit month in the years 1916, 1917, 1918, 1940 – 1949 or after 01.01.1980:

This seems to be a bug in Microsoft backend. We are able to reproduce this issue in any tenant where the regional settings of the SharePoint site are in UTC+1.

Does anyone of you has the same problem in your tenant?

Best regards,

Stefan

​Hello everyone, today we observed a pretty strange behavior of date columns in the new SharePoint lists (= MS Lists layout) in all of our customer tenants. The tenants are in time zone “W. Europe Standard Time” (= UTC + 1) (this is also the setting in the “Regional Settings” of each SharePoint site). When we select a date value before 01.01.1980 and the month is one-digit “1 – 9” (January – September), it shows the date correctly in the EditForm, but in the SharePoint list itself it is displayed in UTC (which means the date is shifted 1 day to our selected date in the EditForm):  However, this only happens when the month has exactly one digit. If it has two digits (10, 11, 12 = October, November, December), the displayed date values in the EditForm and in the SharePoint list are identical, no matter which year was selected:  Even more strange is that the problem with the date differences does not occur when you select a date with a one-digit month in the years 1916, 1917, 1918, 1940 – 1949 or after 01.01.1980:  This seems to be a bug in Microsoft backend. We are able to reproduce this issue in any tenant where the regional settings of the SharePoint site are in UTC+1. Does anyone of you has the same problem in your tenant? Best regards,Stefan  Read More

​