This week, one of our users created a new version of a set of documents in Scroll Documents, as has been done many times.
Unfortunately, this time, the user neglected to change the prefix, and so the "new version" is still in the same tree as the previous one. If they attempt to use the "Change prefix" option, it tries to change the entire tree, not only the single version.
Is there a way to disassociate this errant version?