SharePoint Document Issues

Fix SharePoint Document Library Metadata That Cannot Be Updated

Maira Mehtab Sep 22, 2026 868 views

Question details

The user is unable to edit or update specific metadata values in a SharePoint document library after migrating files and changing column formats.

Product: Microsoft SharePoint
Device & OS: not provided
Scenario: Trying to update metadata values in SharePoint custom text columns (such as Document ID and Staff ID) after the original column format was changed from Number to Text during a migration.
Observed behavior: The values (e.g., 3670.00000000000) are locked and cannot be edited via the SharePoint user interface or by using PnP PowerShell commands.

Before you start

Ensure you have site collection administrator privileges and verify whether the column type was recently modified from Number to Text in the Library Settings.

Solution 1Recommended

Create a Microsoft 365 Support Request for Backend Investigation

Since the issue persists across both the UI and PnP PowerShell after a schema change, it requires backend data and schema investigation by the Microsoft support team.

When SharePoint columns are converted from Number to Text formats, especially during or after a data migration, structural schema errors can occasionally occur in the backend. Because these errors lock the data at the database level, traditional frontend tools like the SharePoint UI or PnP PowerShell scripts cannot resolve the issue.

Log into the Microsoft 365 Admin Center

Navigate to admin.microsoft.com and sign in using your global administrator or SharePoint administrator credentials.

Navigate to the Support module

On the left-hand navigation menu, click on 'Support' and then select 'Help & support' to open the virtual assistant.

Detail your issue

Enter a description of the metadata update failure. Be sure to specify that the column was changed from Number to Text, mention the affected custom columns (like Document ID), and note that PnP PowerShell edits are also failing.

Submit the ticket

Follow the prompts to formally submit the request. This allows the appropriate Microsoft backend team to review tenant logs and correct the schema discrepancy.

For Non-Administrators: If you do not have administrative access to the Microsoft 365 Admin Center, you will need to contact your organization's IT department or SharePoint administrator to open this support ticket on your behalf.

Free Microsoft Office alternative

Try WPS Office for Your Document Management Needs

If you are facing complex backend issues with Microsoft ecosystem tools like SharePoint, consider using WPS Office as a lightweight, free, and highly compatible alternative for handling your daily word processing, spreadsheets, and presentations.

1. Download the software: Visit the official WPS Office website and download the installer for your operating system.
2. Install WPS Office: Run the installation wizard and set up WPS Office on your computer in just a few clicks.
3. Open and edit your files: Launch WPS Office to securely open, edit, and manage all your Microsoft Office documents without format compatibility issues.

Fully compatible with Microsoft Office formats (DOCX, XLSX, PPTX).Easily manage document properties and metadata locally without relying on complex cloud-based schemas.Lightweight installation with a familiar, easy-to-navigate user interface.Free to use, offering seamless offline and local network document management.

microsoft office alternative - wps office

Frequently Asked Questions

Why can't I edit SharePoint metadata after changing a column from Number to Text?

When changing column types in SharePoint, particularly after importing or migrating data, backend schema mismatches can occur. This conflict between the database schema and the frontend column settings locks the metadata fields, preventing updates.

Can I fix locked SharePoint metadata using PnP PowerShell?

Normally, PnP PowerShell is an effective tool for bulk-updating metadata. However, if the issue stems from a deeper schema corruption or backend data lock during a column conversion, PowerShell commands will be rejected just like manual UI updates.

What should I do if I am not an admin and cannot update a document's metadata?

You should contact your organization's IT administrator. They can verify your permission levels and escalate the issue to Microsoft Support if it is determined to be a site-wide backend error.

How do I revert a column type in a SharePoint library?

You can navigate to 'Library Settings' > 'Columns', click on the specific column, and change its type back to the original format. However, if the data is already locked due to schema errors, reverting the type might not resolve the underlying metadata update issue without Microsoft backend support.

Document & File Issues