We have some files which are central repository files that multiple users hit constantly. Our Versions count is set to 25. Typically 25 versions of these files only covers about 2 days of version saves. If someone wants to see what the file looked like last month, that history is long gone. What would be interesting is if a file could be archived automatically every time the version history increments N times. So if you set N=25, then after 25 versions a copy would be generated. Ideally this would be visible through the version history function. It really could be a setting per file or folder rather than globally; most files would not need this treatment.
I suppose with the API we could write something to save off files into an archive folder. Haven't looked into that yet, and wondering if anyone else has done this.
Hi @David Carroll1, thanks for the suggestion! Since your comment is partially looking for suggestions from the community and partially a product idea, we will keep this post as is to hopefully see if other members have thoughts on workarounds for you.
But additionally, please post your idea on managing versions in our ideas section so our products team can assess the idea and other members can vote on it to show if they have that need as well.
Best, - Julie
PS. Help others find answers by selecting "Accept as Solution" if a post answers your question.