How to Fix Different SharePoint Calculated Values Across Browsers
Question details
Users see conflicting results in SharePoint calculated date columns, where the same data displays as 0 in one browser and December 29, 1899 in another.

- Product
- SharePoint
- Device & OS
- not provided
- Scenario
- Viewing and managing SharePoint lists that utilize calculated date columns across different web browsers like Chrome, Edge, and Firefox.
- Observed behavior
- The calculated date column renders inconsistently, showing as 0 for some users while rendering as the default baseline date of December 29, 1899 for others depending on browser formatting and time-zone extensions.
Verify whether the users experiencing the issue are in the same geographical time zone and ask them to temporarily disable their ad-blockers or privacy extensions to rule out immediate script interference.
Disable Browser Extensions and Clear Cache
Time-formatting or privacy extensions can manipulate how SharePoint renders date scripts, causing discrepancies between different web browsers.
Modern web browsers allow extensions that modify how dates and times are displayed on web pages. If an extension overrides SharePoint's native formatting scripts, a raw date value of '0' might incorrectly be parsed as December 29, 1899.
In your web browser (e.g., Chrome or Edge), navigate to the Extensions menu and temporarily toggle off all third-party add-ons, especially those related to time zones, formatting, or privacy blocking.
Open your browser's settings, find the 'Clear browsing data' option, and clear cached images, files, and cookies for all time to ensure you are loading the freshest version of the SharePoint site.
Refresh the SharePoint page and compare the calculated column values. Test this in an alternative browser like Firefox to confirm if the issue is isolated to a specific browser profile.

Verify Regional and Time-Zone Settings
Mismatched site-level and user-level time zone settings can cause date display discrepancies in SharePoint depending on how the browser queries local time.
Review the Calculated Column Formula
Ensure the formula handles blank or null date values properly, as some browsers render empty mathematical dates as Dec 29, 1899.
Manage Data Accurately with WPS Office
If browser-based SharePoint issues continue to disrupt your workflow, consider using WPS Office for your local data and document management. As a lightweight, free alternative to Microsoft Office, WPS Office ensures your spreadsheet data, including complex date calculations, remains consistent across all your devices without relying on web browser rendering quirks.
- 1. Download and Install WPS Office: Visit the official WPS website and download the free installation package for your operating system.
- 2. Open Your Exported Data: Export your SharePoint list to an Excel file and open it directly in WPS Spreadsheets to view accurate date values.
- 3. Manage Formulas Locally: Use WPS Spreadsheets to manage complex calculated columns and ensure your dates format correctly without browser interference.

Frequently Asked Questions
Why does SharePoint sometimes display December 29, 1899?
December 29, 1899 (or December 30, 1899) is the baseline default date in Microsoft's time calculation logic. When a SharePoint calculated column evaluates a blank or null date as '0', it defaults to this historical baseline date.
Can my local computer clock affect SharePoint dates?
Yes. SharePoint dynamically translates time stamps based on the user's regional settings and the computer's local clock. If your local clock is out of sync, dates and times might appear differently for you than for other users.
Is there a formula trick to hide the 1899 date error?
Yes, you can modify your calculated column formula to check for an empty value before performing the calculation. Wrapping your logic in an =IF(ISBLANK([ColumnName]), "", [Calculation]) function will output a blank space instead of an erroneous 1899 date.




