topic Vault Pro 2015 Rename command in Vault Forum

Vault Pro 2015 Rename command

tahdesign1 — Mon, 18 Jul 2016 20:25:39 GMT

I am typing up some instructions on using the rename command and was trying to make examples of when the Vault would restrict you from using it.

At this point it appears to only be restricted if the file itself is checked out.

I did a small test by checking out an assembly but not the child parts.

The Vault explorer interface shows that the child parts are on the workstation but not checked out.

I renamed one of these child parts in the vault and I was allowed to. The Vault explorer interface changed to the new name and the vault status icon now indicated that there was no longer a local copy.

However, there was a local copy of that file with the old name since I still had the assembly open in IV.

So when I checked the assembly in the locally previous named file was still pulled in and deleted. Once in the Vault it was now the new name.

So outside of a file being checked out itself, what else would block the rename command?

Re: Vault Pro 2015 Rename command

brendan.henderson — Tue, 19 Jul 2016 01:45:05 GMT

User permissions, file permissions, file lifecycle. All can effect the ability to rename a file.

Re: Vault Pro 2015 Rename command

tahdesign1 — Tue, 19 Jul 2016 12:36:27 GMT

Sorry should have clarified. I know the permissions and states of the files can but what i was asking is about basic interactions on unreleased files.

So it appears it is only if the specific file is checked out. Even of you have a local copy it ask to refresh before you allowed to edit it.