@@SharePointMaven Yes, right. The thing is : First, I would have introduced this topic _before_ presenting C-O/I (COI = Checking Out/In), because version number are closely related to the workflow of document editing. And second, I would have presented both topics together in a "real world use case". You said in the COI video that according to you, COI was rended useless due to co-authoring (co-edition), but if someone works offline (which still happens nowadays) on his OneDrive local replica of an online SPO document, the COI is very useful. You may be right that someone leaving the company (for vacation or definitively) with docs checked-out is a problem to deal with, right.
I'm setting this up for our company. I was also trying to combine it with a non mandatory built in approval workflow. Right click a file > automate > request sign off. I had cases when signoff, then publish worked fine. But sometimes the published version would be a minor version like 2.1 instead of the expected 2.0 Its hard to reproduce the issue, but because it does happen sometimes, makes it unusable. We only want major versions as published, approved to send the document (in pdf) to the customer. Do you experience the same issue?
@@MrHighvolt I don't know if you were asking me or SPOMaven, but here's an answer : I think that every time I published a document, it got a major version, not a minor. Anyway, you should report a bug to Microsoft next time you face this bug, don't you think?
I have a sharepoint site that has a document with 500 major versions, and I want to limit it to 100 major versions. When updating the number of major versions, will the first 400 versions be deleted or will they be kept? If they are removed, is there a way to recover those versions? Thanks in advance.
From what I understand, they will be deleted. Doubt you can recover them easily. Suggest you think twice before doing this. Not sure if this is due to storage or what, but I would not do this.
A really important questions - Does autosave create a new Minor version if minor versions are enabled? I would hate to open a word doc and leave it open for a day of work , only making a few changes. But autosave has saved every 5 minutes and now created version 1.56 or something? I would hope that when you click in to open a doc and then finally click out of it and save.. that you would only move up one minor version. Can you confirm how and when autosave impacts minor versions?
@@SharePointMaven oh no . so you can have 50 minor versions from one editing session? Thats insane. Why is that the default. why can't it be a minor version for every open and shut. Can you make it one minor version for every check out and check in? is there any other option ?
@@SharePointMaven thank you I kind of started thinking that as well. Trying to help someone who oversees a document where multiple people update normal process is done via email getting lots of updates and she updates. I was trying to think of a better way in sherepoint. I’m wondering if the overarching site has something ticked off so I can’t see all of my revisions as I edit. I did do the check out feature and I am only one testing and doing minor but it’s just stacking them I don’t see ever revision like your screen.
Is there a way to go back in minor versions while keeping the version number. Say Document is version 3.5. And I want to go back to version 3.2 and have the version be 3.2 (if we restore, the version becomes 3.6). So something like the unpublish option but for minor versions?
i have excel file name Contracts-GC.xls with many version history from Januart 2023 to May 2023 now i save another file name Contracts-GC-June29.xls, but all original version history gone form my original file name Contracts-GC.xls, how to see again all verion history of Contracts-GC.xls again
Hi Maven, Can you please explain If I have stored Pdf version of any documents (e.g. SOP 56 Rev 1) and when I have updated copy of the document in Pdf (SOP 56 Rev 2). How can I replace them without breaking the link given to other people? Thanks
