Forum Discussion
MicrosoftVersioning update to Document Libraries in team sites in SharePoint Online and OneDrive for Business
This is not agreeable. We are a small non-profit, and increasing the limit to 100 is an overkill.
OTH I am also unable to understand why the version is bumped when a document is opened? When I open a document from a synced folder on my PC, just to view it, and then close it, it saves it and version bump occurs. The site then shows the history as me having edited the document and people start calling me on why did I change it, when I haven't actually. This is getting insane.
Also, could someone help me understand how minor vs major versioning occurs on auto-save?
Not sure I understand when Office AutoSave does this either but I've seen this in all my customers since it was introduced earlier this year - it is causing havoc with processes where the preservation and tracking of last-accessed and modified is important.
SP has more advanced features around locking items as records (in-place) and other controls which can be applied like AIP/DLP *but* we shouldn't have mitigate behaviours by introducing yet more services and tools for something that should not happen i.e. if i make open a document, but make no changes when it's open, it should not update version and the modified date.
The only way to guarantee it does not happen appears to be force check-in/out and (or) have mandatory metadata in a library - this locks the document prior to committing edits, and then you can 'discard check-out' and have no impact *but* then you lose the ability to coauthor on any document in said library :(
