Forum Discussion
what will happen if we leave the "Keep drafts for the following number of major versions:" unchecked
Great! Yes that makes sense, thank you ChrisWebbTech! My question now is (and this is what I was looking for when I came across this thread) how can we set the number of saved minor versions?
How do I change that 511 default? It is not an option in Library Settings > Versioning.
We have a team that is hitting 511 minor versions and it is stopping them from moving forward unless they publish a major. But they only want to publish a major at certain milestones that they have not yet reached.
Hi ChrisWebbTech and john john
In case you are intersted, I heard back from Microsoft Preimier support. They have confirmed that setting the number of minor versions per major is possible, but not through the SP UI. It has to be done via Powershell.
They sent me the following link with details of how to do it. See example 5.
https://docs.microsoft.com/en-us/powershell/module/sharepoint-pnp/set-pnplist?view=sharepoint-ps
Cheers
Dallas
- That function can now be found here: https://pnp.github.io/powershell/cmdlets/Set-PnPList.html with examples
DallasBland ChrisWebbTech I know this is a bit older threat, but still valid. We face the same as DallasBland. However our problem is not really increasing the versions. 500 is enough in case the last one is deleted, but that is not the case. As it is written here, people cannot work until they publish major, more efficient would be delete the 0.500 so you only get latest 500 versions.
Increasing the version is only pushing away the pain and need to publish it anyway when you reach higher number set by powershell.
It really a problem since with AutoSave you reach 500 version in a couple of hours with 5 users collaborating on a document.
Don't you know how to enforce the version being deleted resp. overwritten ? Is there some uservoice for that if not possible now ? Any help appreciated.
Thanks
Tomas
