Allow change of project for versioned documents

[nxpet]

Hi, it is not possible to move versioned documents to another project, see CS184256. The project field cannot be added to 'Document Model' > 'Version Edit Fields'.

We were reorganizing a project into sub-projects, thats why I wanted to move some of the document (including the corresponding versions/revisions) into a new project. The live document can be moved to a new project, but the versioned documents cannot be moved. They must remain in their origin project forever, which makes it very unflexible.

I suggest to allow to change the project of versioned items as well.

Regards

Timo

[mrump]

I totally agree. This would be a great help when using the Document Versioning Feature

[SM_10187717]

It is absolutely essential function! Moving Live Item to another Project while Versioned Items are stick on the project where they were created makes whole document inconsistent. I'd like to know what were developers suggestions for such a solution. Is it a kind of limitation of information model used? If not then I would ask not to wait for "votes" but just to fix it and make it in accordance with common sense.

[mrump]

Hi @SM_10187717 ,

good to see that others share the pain 🙂. For the matter of data consistency IMHO there is no problem, as all relies on the ID, not the project.

Our intention was originally to "split" projects into WORKING and LIBRARY/RELEASED projects that have different permissions and to have a release process where a versioned Document is moved from one project o another.
Currently this basic process is undoable in RV&S.

[amund]

This is such an important function!
Old (versioned) documents remain useless in projects and are being used by mistake (because they are in the active project).
This is a big problem especially in the library.

This idea has been around for so long now. When will it finally be implemented?