05-01-2020 09:41 AM
05-01-2020 09:41 AM
I have searched every crevice of the internet and cannot find a solution to my issue with discussion board timestamps on SharePoint online; can someone please help me!
The issue: When a user creates a post in the discussion board, it lists the post name and "created" time accurately. However, when you click the post name to view the discussion, all listed times are 7 hours earlier than the actual time. Here are screenshots of this issue in action:
Test Post is created with a 4:26 PM timestamp (Pacific Standard Time)
Test Post thread shows 9:26 AM timestamp. Note the tool-tip lists the correct 24-hour timestamp.
From all the forums I've read through there were two obvious placed to check; personal regional settings in Delve, and administrator regional settings for the site. The admin settings are configured for Pacific Standard Time (as you can see from the example below) and my Delve account has been set to use those settings configured by the administrator (me).
SharePoint site settings:
My personal Delve settings:
I have tried updating my Office 365 regional settings through PowerShell, confirming search schema for created and modified dates, I tried to manually adjust the "Flat" view for the post to format the create and modified columns but nothing works. We're trying to get a discussion board set up for parents coping with home-schooling during the COVID pandemic, and I can't put this discussion board into production if users are going to be asking me everyday why their post time is incorrect. Any help with this would be absolutely appreciated. Thank you!
05-01-2020 09:58 AM
@ThomasShaw As I posted this I questioned whether I actually did confirm the crawl properties for "created" so I checked and they weren't all mapped. In the image below, the highlighted properties were not mapped to anything so I added in Created and re-indexed the site for good measure. I'll post an update this afternoon. Hopefully by then something will change.
06-03-2020 08:52 AM
@Mara Lanz I honestly thought I was alone so we just switched to Microsoft Teams for this specific case. I did however just create another discussion board and it looks like the fix was applied and works!! Thank you for going down that avenue and taking the time to reply, I really appreciate it. It's nice to know we have that functionality back.