logo
search
SharePoint Document Issues

How to Fix Incorrect SharePoint News Post Date (January 1, 1)

Adam DavisAdam Davis Oct 10, 2026 869 views

Question details

The user needs to correct a SharePoint news post publication date that is displaying an erroneous placeholder date, causing the post to appear in the wrong order.

How to Fix an Incorrect SharePoint News Post Date
Product
Microsoft SharePoint
Device & OS
not provided
Scenario
Publishing or managing a news post within a SharePoint Site Pages library.
Observed behavior
The published news post incorrectly displays its date as "January 1, 1" instead of the actual publication date, shifting its chronological position in the news web part.
Before you start

Ensure you have the PnP PowerShell module installed on your computer and verify that you possess Site Collection Administrator permissions for the affected SharePoint site before running any scripts.

Solution 1Recommended

Update the FirstPublishedDate Field Using PnP PowerShell

The most effective and permanent way to fix the date bug is by updating the read-only FirstPublishedDate property via a PnP PowerShell script.

Because the FirstPublishedDate field is read-only in the standard SharePoint user interface, it cannot be edited manually from the page properties. Using PnP PowerShell allows you to bypass this limitation and inject the correct timestamp.

1
Open PowerShell

Launch the PowerShell application on your computer with Administrator privileges.

2
Connect to your SharePoint site

Run the command 'Connect-PnPOnline -Url [YourSiteURL] -Interactive', replacing [YourSiteURL] with the actual URL of your SharePoint site, and sign in.

3
Find the Page ID

Navigate to your SharePoint 'Site Pages' library, locate the affected news post, and note its unique Item ID.

4
Run the Update Command

Execute the command 'Set-PnPListItem -List "Site Pages" -Identity [PageID] -Values @{"FirstPublishedDate"="2024-03-14T12:00:00Z"}'. Be sure to replace [PageID] with your specific ID and use the correct ISO 8601 formatted date.

Update the FirstPublishedDate Field Using PnP PowerShell
Date Format Requirement: PowerShell requires strict ISO date formatting (e.g., YYYY-MM-DDTHH:MM:SSZ). Standard formats like '2024-03-14' may fail to process.
Free Microsoft Office alternative

Edit and Collaborate on Documents Easily with WPS Office

While SharePoint handles your team's intranet sites, WPS Office is the perfect free, lightweight alternative for creating, editing, and collaborating on your daily office documents. Enjoy a familiar interface and seamless migration without the heavy subscription fees of Microsoft Office.

  1. 1. Download the Installer: Visit the official WPS Office website and download the free software package tailored for your operating system.
  2. 2. Install WPS Office: Run the installer and follow the quick on-screen instructions to set up the lightweight application.
  3. 3. Open Microsoft Formats: Double-click any .docx, .xlsx, or .pptx file to open, edit, and save it effortlessly within WPS Office.
Fully compatible with Microsoft Word, Excel, and PowerPoint formatsFree, lightweight, and fast-loading office suiteFamiliar user interface requires zero learning curveBuilt-in PDF editing and seamless cloud collaboration
microsoft office alternative - wps office

Frequently Asked Questions

Why does my SharePoint news post date show as January 1, 1?

This is caused by a known SharePoint bug where the 'FirstPublishedDate' field fails to update correctly in the background upon publication. Because the system lacks a valid date, it defaults to the absolute minimum calendar value (January 1, 1).

Can I edit the FirstPublishedDate directly from the SharePoint user interface?

No, the FirstPublishedDate field is completely read-only within the standard SharePoint list and page properties interface. It can only be modified programmatically using administrative tools like PnP PowerShell.

What is the correct date format for updating SharePoint list items in PowerShell?

When updating date fields like FirstPublishedDate via PowerShell, you must use the strict ISO 8601 date format (for example, '2024-03-14T12:00:00Z'). Using standard shorthand dates will often result in a failure to update.