SharePoint Document Issues

Fix People Search Core Results Web Part Changes Not Saving in SharePoint

Maira Mehtab Sep 21, 2026 869 views

Question details

Users are unable to save or apply changes made to the People Search Core Results web part on a SharePoint Online Enterprise Search site, resulting in a blank page with no search data.

Product: SharePoint Online
Device & OS: not provided
Scenario: Modifying web part parameters such as the search query, display-template settings, or hiding the 'Alert Me' option, and attempting to publish the page.
Observed behavior: The test query successfully returns results within the editor, but after selecting Apply, OK, Save, and Check In, the saved page shows no data and the web part updates are not reflected.

Before you start

Before troubleshooting, verify that your test query returns the expected results within the web part editor and check the Microsoft 365 admin center for any active service health incidents affecting search functionality.

Solution 1Recommended

Check Microsoft 365 Service Health for Search Incidents

Backend service outages or degradation can cause intermittent failures or latency in custom SharePoint and Microsoft Graph search solutions.

SharePoint custom search web parts rely heavily on Microsoft's backend infrastructure. If there is an active service incident (such as MO861941), changes may fail to save, or queries may fail to render live data despite working in test mode.

Log in to the Admin Center

Navigate to the Microsoft 365 admin center using an administrator account.

Navigate to Service Health

In the left-hand navigation menu, click on 'Health' and then select 'Service health'.

Review Active Incidents

Look for any active advisories or incidents related to SharePoint Online, Microsoft Graph, or search latency (e.g., MO861941). If an incident is active, wait until Microsoft resolves the issue before attempting to save web part changes again.

Contacting Microsoft Support: If you confirm your issue coincides with an active incident that remains unresolved for an extended period, consider opening a support ticket directly with Microsoft.

Solution 2

Isolate Web Part Settings and Document Configurations

Testing specific configurations individually helps determine if a particular setting, such as a custom display template, is breaking the page rendering.

Free Microsoft Office alternative

Looking for a Reliable and Lightweight Office Suite?

If you frequently encounter intermittent issues or complex configurations within the Microsoft ecosystem, consider trying WPS Office. It provides a lightweight, fast, and highly compatible workspace for all your document management needs.

1. Download the Installer: Visit the official WPS Office website and download the free installation package for your operating system.
2. Install WPS Office: Run the installer and follow the quick on-screen instructions to set up the software.
3. Open and Edit Documents: Launch WPS Office to instantly open, edit, and save your existing Microsoft Office files without formatting loss.

Free, lightweight, and fast-performing office suiteFully compatible with Microsoft Word, Excel, and PowerPoint formatsFamiliar, easy-to-use interface requiring no learning curveBuilt-in PDF editing and comprehensive cloud collaboration tools

Frequently Asked Questions

Why does my SharePoint web part test query work but the page shows no data?

This commonly occurs if there is a backend Microsoft service incident affecting live search indexing, if the SharePoint page was not properly checked in and published, or if a customized display template contains code errors that only break during full page rendering.

How do I properly save and apply changes to a SharePoint Search Web Part?

To ensure changes are applied, you must edit the web part properties, make your modifications, click 'Apply' followed by 'OK' in the web part tool pane, and then explicitly click 'Save' and 'Check In' (or 'Publish') on the main page ribbon.

What was service incident MO861941?

MO861941 was a specific Microsoft service incident that caused latency and intermittent data retrieval failures for custom search solutions utilizing Microsoft Graph and SharePoint Online.

Document & File Issues