How to Fix SharePoint Cannot Save or Check In Document Due to Missing Properties
Question details
The user is unable to save or check in documents in a SharePoint library because the system incorrectly reports that required properties are missing.

- Product
- Microsoft SharePoint
- Device & OS
- not provided
- Scenario
- Attempting to save or check in a file to a SharePoint document library that enforces required metadata columns.
- Observed behavior
- SharePoint blocks the save or check-in process, displaying an error about missing required properties even when all visible metadata fields have been fully populated.
Ensure you have double-checked the document's properties panel to confirm all required fields (marked with an asterisk) are actually filled out. Gather screenshots of the filled metadata, the exact error message, and note the affected file names before escalating the issue.
Escalate to Microsoft Support via Microsoft 365 Admin Center
Since the metadata is visibly complete but the system still blocks the check-in, this indicates a backend syncing or database caching issue that requires remote troubleshooting by Microsoft Support.
When standard user-level checks fail to resolve false missing properties errors, the issue is often rooted in the SharePoint backend environment. Only Microsoft Support has the necessary access to investigate backend logs and perform advanced remote troubleshooting to fix the corrupted metadata sync.
Take screenshots or a screen recording showing that the required properties are filled out but the check-in still fails. Note the exact timestamps and the URL of the affected document library.
Reach out to your organization's IT department or Microsoft 365 administrator, providing them with the collected details and recordings.
Have your administrator log in to the Microsoft 365 admin center, navigate to the Support section, and create a new online support request with the collected logs.

Temporarily Make the Column Optional (Workaround)
If you urgently need to check in the document and have sufficient site permissions, you can temporarily disable the strict requirement on the problematic column.
Try WPS Office for Seamless Document Management
If complex metadata requirements and sync errors in Microsoft Office and SharePoint are slowing down your productivity, consider switching to WPS Office. It provides a lightweight, highly compatible, and user-friendly alternative for viewing, editing, and managing your essential documents without the heavy overhead.
- 1. Download the installer: Visit the official WPS Office website and click the free download button for your operating system.
- 2. Install the software: Run the downloaded installation file and follow the simple on-screen instructions to set up WPS Office on your device.
- 3. Open and manage your files: Launch WPS Office and directly open your existing Microsoft Office documents to start editing immediately with full formatting preserved.

Frequently Asked Questions
Why does SharePoint say my document is missing properties when they are already filled out?
This false error typically occurs due to backend synchronization delays, corrupted site columns, or browser caching issues. The visual interface may show the data, but the SharePoint server hasn't registered the metadata update successfully.
Can I force a document to check in if SharePoint blocks it?
SharePoint prevents check-ins if strict column requirements are not met. You cannot bypass this as a standard user. You must either fulfill the property requirements or ask a Site Administrator to temporarily make the column optional.
How do I find out who my Microsoft 365 administrator is?
Your Microsoft 365 administrator is usually the IT support team or the person who issued your work email address. You can also try looking up your organization's IT helpdesk portal or checking your Microsoft account profile details for support contacts.
Does clearing the browser cache fix the missing properties error?
Sometimes. If the issue is caused by a stale browser session displaying outdated library settings, clearing your browser cache and cookies or using Incognito/InPrivate mode might resolve the conflict and allow the properties to save properly.




