'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix Microsoft Lists Showing Dates One Day Earlier in List View
Question details
Users need to resolve a discrepancy where dates in Microsoft Lists appear one day earlier than the actual date entered.
- Product
- Microsoft Lists
- Device & OS
- not provided
- Scenario
- Viewing date columns in the primary list view versus opening the specific item details to view the date.
- Observed behavior
- The list view displays a date one day behind the actual date shown when the item is opened, often affecting multiple users and organizations simultaneously.
Ensure you have site owner or administrator permissions to check the site's regional settings and verify that your browser and system time zones match your Microsoft 365 account settings.
Verify Regional Settings and Escalate to Microsoft Support
Check the time zone configurations for both the site and the user account, and report widespread issues to Microsoft Support for a backend fix.
Because this discrepancy often affects multiple users across different organizations simultaneously, it is frequently caused by a Microsoft service update or a bug in how time zones are handled in the web rendering of the List view.
Navigate to Site Settings (gear icon) > Site Administration > Regional settings. Verify that the time zone selected accurately reflects your organization's primary location.
Click your profile picture in the top right of Microsoft 365, select 'View account', go to 'Settings & Privacy', and ensure your personal Time zone matches the site's regional settings.
If the time of day is not strictly required, go to List Settings, click on the affected date column, and ensure it is set strictly to 'Date Only' rather than 'Date & Time'. This can sometimes prevent UTC conversion offsets.
Since this is often a known service-side bug, document examples (e.g., screenshots comparing the list view and the item view) and ask your Microsoft 365 Administrator to open a service request in the Microsoft 365 admin center.
Try WPS Office for Reliable Spreadsheet and Data Management
If online service bugs are interrupting your data tracking workflow, WPS Office offers a free, lightweight, and highly compatible desktop alternative. Manage your lists and datasets using WPS Spreadsheet with accurate offline date handling and perfect Microsoft Excel compatibility.
- 1. Download WPS Office: Visit the official WPS website to download and install the free WPS Office suite.
- 2. Export Your List: Use the 'Export to Excel' or 'Export to CSV' feature in Microsoft Lists to download your data locally.
- 3. Manage Data Locally: Open the exported file in WPS Spreadsheet to manage your dates and records accurately without web rendering bugs.
Frequently Asked Questions
Why does the date change when I export Microsoft Lists to Excel?
If time zone settings differ between the SharePoint site (or Microsoft Lists backend) and your local machine, exporting to Excel can sometimes shift dates by a few hours based on UTC conversions. This shift can cross the midnight boundary, causing the displayed day to change.
Can I fix the Microsoft Lists date bug by changing my column settings?
Changing the column format from 'Date and Time' to 'Date Only' can sometimes mitigate time-zone offset issues. However, if a Microsoft service update bug is causing the list view to render incorrectly, the backend will still show the wrong date regardless of the column setting.
How do I know if this date issue is a Microsoft backend bug?
If multiple users in your organization—and especially users in other organizations—are experiencing the exact same one-day offset in the List view compared to the item details, it is highly likely a service-side bug requiring a Microsoft patch rather than a local configuration error.
