Timeline for incorrect of sharepoint 2016 datetime field value
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 17, 2017 at 7:47 | comment | added | GIANGPZO | @Danny'365CSI'Engelman,@Semushin Dmitrii, I have just found out the problem, please see my answer. thanks. | |
| Apr 17, 2017 at 7:44 | vote | accept | GIANGPZO | ||
| Apr 17, 2017 at 7:44 | answer | added | GIANGPZO | timeline score: 0 | |
| Apr 14, 2017 at 11:17 | comment | added | Danny '365CSI' Engelman | TimeStamp difference? SharePoint starts counting at 31/12/1899 your C# code at 1/1/1900? | |
| Apr 14, 2017 at 8:32 | comment | added | GIANGPZO | @Danny'365CSI'Engelman the timezone is the same in both Server and Client. | |
| Apr 14, 2017 at 7:31 | comment | added | Danny '365CSI' Engelman | Most likely a timezone difference between Server and Client you have to deal with programmatically | |
| Apr 14, 2017 at 6:20 | comment | added | GIANGPZO | yes, I did, but have no result. | |
| Apr 14, 2017 at 4:56 | comment | added | Semushin Dmitrii | Do you use Convert.ToDateTime(item[dateField]) or what? | |
| Apr 14, 2017 at 3:55 | history | asked | GIANGPZO | CC BY-SA 3.0 |