Avoid multiple versions with every save | Voters

Avoid multiple versions with every save

under review

Dahlia Shuhaibar

Currently, if you open a document from LW to work on it, it creates a new "version" every time you click save. This feature would create a new version only when the document is closed (rather than needing to save a copy and upload the copy.)

February 22, 2022

LexWorkplace Product Team

Merged in a post:

Versions

Paula Gil

Would like only one version of a current document when saved with new changes. Every time document is saved, it saves to a new version.

April 16, 2024

Patricia L.

Agreed!

Ismael N.

Having just onboarded to LexWorkplace, we just encountered this "annoyance." Coming from Worldox, we are used to creating a new version only ON DEMAND, not with every save. We have multiple Excel spreadsheets that people use all day, every day. One of our users already has 11 versions of a file. 
I see from these comments that some people like this feature. We do not. Having the "Save as a new version" ON EVERY SAVE should at least be a feature that can be toggled on and off. 
Ideally, hitting SAVE should save over the existing file, and SAVE AS should be the option to create a new version.
This request has been here since 2022, please add it to the pipeline.

LexWorkplace Product Team

marked this post as

under review

LexWorkplace Product Team

Merged in a post:

Version Control

Alexandra J.

A new version should not be created with every save. Save should keep the same version and save as should create a new version.

August 23, 2022

LexWorkplace Product Team

Thank you for the input Alexandra, this is helpful.

I'm going to merge this with the existing/same Feature Request.

Tim Atler

Alternatively, saving during a session could be version 1.1, 1.2, etc., and then a new open/close session could be version 2.1, 2.2, etc. To keep things tidy in the versions window of the properties screen, the "decimal" versions could be collapsible into a single version (you could use the customary triangle icon on the side) with the latest decimal version showing at the top level. I hope that makes sense.

I'd also like to add that we really like the creation of a new version on every save. In our practice, we often spend a lot of time in the same document, so the sessions can be long. The new versions with each save allows us to go back to earlier versions in a session, if necessary, or to avoid losing data if there is a crash. In other words, it serves as another layer of backup. It also creates a nice audit trail showing when a document was worked on and for how long. If the developers are inclined to change the approach to versioning, we hope they will make versioning on each save an option that can be toggled on or off.