'%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 SharePoint Metadata Fields Not Updating After Migration
Question details
Users are unable to edit or update certain SharePoint document library metadata fields, which display incorrect decimal values (e.g., 3670.00000000000) after completing a migration.
- Product
- SharePoint Online
- Device & OS
- not provided
- Scenario
- Managing document library metadata and column properties after completing a data migration to SharePoint.
- Observed behavior
- Metadata fields are locked from editing via the SharePoint Online UI or PnP PowerShell and display incorrect decimal formats due to unsynchronized Number-to-Text column changes.
Ensure you have gathered the exact library URLs, affected item IDs, and details of your recent migration process before attempting to troubleshoot or contacting support.
Contact Microsoft 365 Support for Backend Synchronization
Because the Number-to-Text column type changes failed to synchronize across libraries during migration, this issue requires backend investigation and correction by Microsoft Support.
This metadata error originates from a mismatch in column types generated during the migration process. Because the affected fields become fully locked on the user end, standard troubleshooting methods via the SharePoint UI or PnP PowerShell will not resolve the issue.
Compile the affected library URLs, content type details, specific item IDs, migration history, and examples of the incorrect decimal values.
Log in to the Microsoft 365 admin portal. Note that you must have administrator privileges to perform this step.
Open a new support ticket providing all the gathered details. If you are not an administrator, pass this information to your IT department so they can submit the request on your behalf.
Seamlessly Manage Migrated Office Files Locally with WPS Office
While waiting for Microsoft Support to resolve your SharePoint backend issues, you can download your documents and manage them locally. WPS Office provides a lightweight, highly compatible, and free alternative to Microsoft Office for all your editing needs.
- 1. Download and install: Visit the official WPS website to download the free installation package for your operating system.
- 2. Open SharePoint files locally: Download your affected documents from the SharePoint library and open them directly in WPS Office.
- 3. Edit and save: Make your necessary edits offline and save the documents in standard Microsoft formats until the SharePoint metadata sync is fixed.
Frequently Asked Questions
Why do my SharePoint text columns display decimal numbers after a migration?
This occurs when columns are migrated from a Number type to a Text type, but the system fails to synchronize the change correctly across all document libraries, causing integer values to display with extended decimals like 3670.00000000000.
Can I fix the locked SharePoint metadata using PnP PowerShell?
No. In this specific post-migration failure scenario, the fields become completely locked and cannot be updated using either the standard SharePoint Online interface or PnP PowerShell scripts.
What information does Microsoft Support need to fix this issue?
To expedite the backend investigation, you should provide the library URLs, content type details, affected item IDs, your migration history, and concrete examples or screenshots of the incorrect values.
