Sharepoint List Web Part says the Year 1899 from internal Created Date - worked, but now its 1899

%3CLINGO-SUB%20id%3D%22lingo-sub-1388923%22%20slang%3D%22en-US%22%3ESharepoint%20List%20Web%20Part%20says%20the%20Year%201899%20from%20internal%20Created%20Date%20-%20worked%2C%20but%20now%20its%201899%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1388923%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20I've%20tried%20to%20find%20the%20answer%20for%20this%20problem%20and%20while%20I%20find%20the%20same%20symptom%2C%20I%20can't%20find%20anyone%20with%20the%20same%20problem%2Fsolution.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20a%20sharepoint%20site%20that%20collects%20hours%20from%20a%20number%20of%20sources%20for%20a%20live%20time%20logging%20system%2C%20up%20until%20yesterday%20things%20were%20find%20then%205%20date%20submissions%20all%20show%20in%20a%20web%20part%20as%20having%20the%20date%2031%2F12%2F1899%2C%20which%20as%20i%20read%20is%20the%20expected%20behaviour%20when%20using%20a%20blank%20date%20field.%20However%20this%20field%20looks%20at%20the%20system%20'Created'%20field%2C%20therefore%20cannot%20be%20blank%20and%20when%20looked%20at%20outside%20the%20web%20part%2C%20in%20the%20list%20view%20the%20dates%20are%20fine.%20Strangely%20the%20web%20part%20still%20see's%20the%20entries%20as%20the%20most%20recent%20as%20this%20view%20is%20sorted%20by%20the%20created%20date.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20insights%20you%20may%20have%20would%20be%20greatly%20appreciated%2C%20I'm%20pretty%20sure%20my%20team%20aren't%20working%20in%20the%20Victorian%20age.%20Thank%20you.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Siewake_0-1589443634928.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F191594i8E05C7FDC8FC8263%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22Siewake_0-1589443634928.png%22%20alt%3D%22Siewake_0-1589443634928.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1388923%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1389907%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%20List%20Web%20Part%20says%20the%20Year%201899%20from%20internal%20Created%20Date%20-%20worked%2C%20but%20now%20its%20189%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1389907%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F667445%22%20target%3D%22_blank%22%3E%40Siewake%3C%2FA%3E%26nbsp%3Bas%20a%20test%20if%20you%20change%20that%20site%20%22locale%22%20settings%20does%20it%20show%20properly%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1390048%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%20List%20Web%20Part%20says%20the%20Year%201899%20from%20internal%20Created%20Date%20-%20worked%2C%20but%20now%20its%20189%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1390048%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F63424%22%20target%3D%22_blank%22%3E%40Bruno%20Aleixo%3C%2FA%3EYes%20it%20does%2C%20setting%20to%20a%20locale%20with%20a%20US%20style%20date%20format%20displays%20the%20inteded%20result%20(2020!)%20for%20that%20locale.%20Thank%20you%20for%20taking%20the%20time%20to%20answer%20here.%20It%20doesn't%20exactly%20solve%20my%20problem%20but%20it%20gives%20me%20hope%20that%20there%20is%20a%20simple%20solution%20here.%20I'm%20trying%20to%20get%20the%20UK%20version.%20I've%20tried%20a%20few%20so%20far%2C%20hopefully%20I'll%20find%20one%20that%20I%20can%20just%20put%20up%20with.%20Thanks%20for%20the%20pointer.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1390063%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%20List%20Web%20Part%20says%20the%20Year%201899%20from%20internal%20Created%20Date%20-%20worked%2C%20but%20now%20its%20189%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1390063%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F667445%22%20target%3D%22_blank%22%3E%40Siewake%3C%2FA%3E%26nbsp%3Bthanks.%20we%20are%20working%20on%20a%20fix%20for%20this%20issue%20and%20should%20be%20fixed%20soon.%20While%20that%20does%20not%20happen%20the%20workaround%20is%20the%20best%20option.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1390080%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%20List%20Web%20Part%20says%20the%20Year%201899%20from%20internal%20Created%20Date%20-%20worked%2C%20but%20now%20its%20189%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1390080%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F63424%22%20target%3D%22_blank%22%3E%40Bruno%20Aleixo%3C%2FA%3EAre%20there%20any%20further%20details%20of%20the%20issue%3F%20I%20may%20be%20happy%20to%20live%20with%20it%20until%20a%20fix%20can%20be%20made%2C%20it%20would%20upset%20my%20main%20users%20more%20to%20change%20the%20date%20format%20on%20the%20main%20lists%20in%20this%20site%20to%20a%20non-regional%20format%20and%20cause%20confusion%20between%20systems.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1390082%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%20List%20Web%20Part%20says%20the%20Year%201899%20from%20internal%20Created%20Date%20-%20worked%2C%20but%20now%20its%20189%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1390082%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F667445%22%20target%3D%22_blank%22%3E%40Siewake%3C%2FA%3E%26nbsp%3BIts%20a%20visual%20issue%20on%20the%20group%20by.%20If%20you%20verify%20the%20items%20themselves%20they%20have%20the%20correct%20dates.%20Another%20workaround%20would%20be%20to%20group%20by%20a%20different%20column.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1390206%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%20List%20Web%20Part%20says%20the%20Year%201899%20from%20internal%20Created%20Date%20-%20worked%2C%20but%20now%20its%20189%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1390206%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F63424%22%20target%3D%22_blank%22%3E%40Bruno%20Aleixo%3C%2FA%3E%26nbsp%3B%20Thank%20you%20so%20much%2C%20knowing%20that%20I%20have%20made%20a%20new%20column%20called%20Logged%20which%20is%20a%20calculated%20column%20of%20the%20%3D%5BCreated%5D%20and%20it%20works%20like%20that%20-%20so%20problem%20solved%20for%20now.%20Thanks%20for%20your%20help%2C%20I%20could%20have%20gone%20on%20forever!%20-%20Simon%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hi, I've tried to find the answer for this problem and while I find the same symptom, I can't find anyone with the same problem/solution.

 

We have a sharepoint site that collects hours from a number of sources for a live time logging system, up until yesterday things were find then 5 date submissions all show in a web part as having the date 31/12/1899, which as i read is the expected behaviour when using a blank date field. However this field looks at the system 'Created' field, therefore cannot be blank and when looked at outside the web part, in the list view the dates are fine. Strangely the web part still see's the entries as the most recent as this view is sorted by the created date.

 

Any insights you may have would be greatly appreciated, I'm pretty sure my team aren't working in the Victorian age. Thank you.

 

Siewake_0-1589443634928.png

 

6 Replies
Highlighted

@Siewake as a test if you change that site "locale" settings does it show properly ?

Highlighted

@Bruno AleixoYes it does, setting to a locale with a US style date format displays the inteded result (2020!) for that locale. Thank you for taking the time to answer here. It doesn't exactly solve my problem but it gives me hope that there is a simple solution here. I'm trying to get the UK version. I've tried a few so far, hopefully I'll find one that I can just put up with. Thanks for the pointer.

Highlighted

@Siewake thanks. we are working on a fix for this issue and should be fixed soon. While that does not happen the workaround is the best option.

Highlighted

@Bruno AleixoAre there any further details of the issue? I may be happy to live with it until a fix can be made, it would upset my main users more to change the date format on the main lists in this site to a non-regional format and cause confusion between systems.

Highlighted

@Siewake Its a visual issue on the group by. If you verify the items themselves they have the correct dates. Another workaround would be to group by a different column. 

Highlighted

@Bruno Aleixo  Thank you so much, knowing that I have made a new column called Logged which is a calculated column of the =[Created] and it works like that - so problem solved for now. Thanks for your help, I could have gone on forever! - Simon