Moving documents between workspaces
AnsweredHas anyone use the moving documents between workspace functionality? If so how was your experience?
I did this just recently and was excited then went into a dreadful mode- why because I had to reset permissions (specific/detailed permissions) for 10 documents. I think an established document (permissions) should maintain the permissions when moved to another workspace.
Also, think should give more clarity on freezing document option when moving to another workspace. At least freezing keeps a copy of the document (including permissions) in original space (i think it does). I chose not to freeze-not realizing i didn't include all linked documents when moving. So didn't have the option to retry the move with all linked documents.
I did this just recently and was excited then went into a dreadful mode- why because I had to reset permissions (specific/detailed permissions) for 10 documents. I think an established document (permissions) should maintain the permissions when moved to another workspace.
Also, think should give more clarity on freezing document option when moving to another workspace. At least freezing keeps a copy of the document (including permissions) in original space (i think it does). I chose not to freeze-not realizing i didn't include all linked documents when moving. So didn't have the option to retry the move with all linked documents.
0
-
I ran into this same problem when I copied narrtatives and I have about 60 narratives. All had to have permissions reset because of the way I copied them. 0
Similar experience. Luckily, we didn't have a lot of documents to migrate to the new workspaces we created. For documents that were already completed, i didn't reset the permissions since they were already frozen. Just gave all users view access. But resetting the permissions on the current documents was tedious. in some cases, I could apply permission sets to make it faster, but for the more granular permission grids, i just did it manually. Agreed that a migration option that actually moved the history, comments, permissions, etc would be preferable (a true move rather than a project copy). I realize that there are challenges here because the same users may not exist in both workspaces, but it seems like there could be a way of resolving that with a generic user, or prompting you for users that need to be added to the new ws. Also, we ran into issues where people didn't realize that the projects had been moved and continued to work in the old workspace because they were accessing the files through their recent items (auto-freezing the docs in the old workspace would have been nice. that may be a newer option because i don't remember seeing it).
All that to say, it wasn't a great experience. but thankfully was a 1-time thing.-1
I have requested several times for the ability to retain history in documents that get moved between workspaces. We have several projects, such as policies and procedures, that don't get rolled, they are just continually updated and we need to retain the history. 0Please sign in to leave a comment.
Comments
3 comments