Versioning library content: new version vs. edited version number
A building product or construction in a library has a version number. There are two different ways to change it, and they do not do the same thing.
New version
Section titled “New version”“New version” creates a completely new entry with the same GUID and owner, but a new version number. The old version stays alongside it unchanged, and every project that already references the old version keeps pointing at it, with the data it had. This is how a library can evolve without changing the result of calculations that have already been made.
Edit version number
Section titled “Edit version number”“Edit version number”, by contrast, only changes the number on the existing entry. No new version is created, and because it is the same entry, all existing references automatically follow along to the new number. The app’s own help text says it directly: “This does not create a new version: it only changes the number of the current one. If you want to keep the existing version, use ‘New version’.”
It is precisely because the two actions resemble each other that the confusion is common. A user who wants to correct an error without affecting earlier calculations should use “New version”. A user who just wants to rename a version number, for example because it was set incorrectly by mistake, should use “Edit version number”.
Conditions for a new version
Section titled “Conditions for a new version”A new version requires write access to the owner of the content, and that the new version number differs from the existing one. If both conditions are not met, the app rejects the attempt with the message “New version is not possible: you either do not have write access to the owner, or the current version cannot be incremented.”