'%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)
How to Edit SharePoint Document Columns Without Creating a New Version
Question details
The user wants to modify document library metadata and columns in SharePoint without triggering the creation of a new document version.
- Product
- Microsoft SharePoint
- Device & OS
- not provided
- Scenario
- Editing document properties or metadata in a SharePoint document library where version history is enabled.
- Observed behavior
- Native SharePoint automatically generates a new document version whenever document properties or column values are changed.
Verify your current SharePoint site permissions and check the document library versioning settings configured by your administrator before attempting to modify metadata.
Understand Native SharePoint Versioning and Restore Earlier Versions
Since native SharePoint does not allow metadata edits without version creation, you can manage versions or restore previous ones if unwanted metadata versions are created.
SharePoint's versioning system is designed to capture all changes made to a file, which includes both the actual file content and its associated properties or columns. Modifying any column will inevitably bump the version number.
Navigate to your SharePoint document library, click the ellipsis (...) next to the document you want to check, and select 'Version History' from the context menu.
Look at the version list to see which versions were created solely due to property or column changes. The modified date and user will be logged.
If a metadata change caused an unwanted version update, click the drop-down arrow next to the date of an earlier version and select 'Restore' to revert.
Utilize Third-Party SharePoint Applications or Custom Solutions
For advanced revision tracking that separates metadata edits from document edits, custom development or third-party tools are required.
Looking for a Lightweight Document Solution? Try WPS Office
While SharePoint handles complex server-side versioning, local document editing and offline collaboration can be streamlined with a fast, lightweight office suite. WPS Office provides excellent compatibility with Microsoft formats without the heavy system requirements.
- 1. Download the software: Visit the official WPS Office website and click the free download button for your operating system.
- 2. Install WPS Office: Run the downloaded installer and follow the simple on-screen instructions to complete the setup.
- 3. Open your documents: Double-click any Microsoft Office file on your computer to open, edit, and save it instantly using WPS Office.
Frequently Asked Questions
Can I disable versioning for metadata only in SharePoint?
No, SharePoint's native versioning applies to both the document file and its associated properties or columns together. Modifying either element will automatically create a new version.
How do I turn off version history completely in a SharePoint document library?
Navigate to Library Settings > Versioning settings. Under the 'Document Version History' section, select 'No versioning' and click OK. Note that this disables versioning entirely for the library, meaning no previous versions of files will be saved.
Is there a way to track document changes separately from metadata changes?
Native SharePoint combines document content and metadata updates into a single version history log. To track them separately, you would need to implement specialized third-party document management applications or custom SharePoint developer solutions.
Will changing a document's file name create a new version in SharePoint?
Yes. The document name is considered a core property/column value. Renaming the file will trigger the creation of a new version in the version history if library versioning is enabled.
