We are trying to figure out a workflow for having our central Revit 2017 central files work with Vault Professional 2017. Revit central files are currently stored on a network folder. The network folder location of the Revit files is currently mapped to a folder location in the Vault.
As of right now the files open from the network folder. Upon synchronization, as set by the settings, they are uploaded to Vault. The issue we have is that we have no way of locking down the Revit files using the power of Vault. The "Open from Vault" feature on the ribbon within the Revit program does not work. When used, it opens a read only file from the C: Drive as this is the working folder in Vault. Unfortunately, in order to change the working folder we would have to remove the enforcement of the C: Drive working folder location, which we would like to avoid. Is there any work around to this issue?
Hi, @Anonymous,
The following is from vault perspective on locking files but it is not a recommended solution. Revit Experts may able to offer some help on how to manage locks from Revit.
If the master Revit file is set to "Read-only" from Vault (Select file > Details > Security > Add everyone and select Allow for "Read"), the user's changes will NOT be synchronized to vault though the central Revit file in Network folder is able to get the updates from the clients.
Let's say Your central Revit file stays in a network path \\Server\Share\CentralRevit.rvt. Instead of "opening the file from Vault" you can open the file from the network path. Please remember to choose "create new local" option. Note the file name is automatically changed to "central filename" + the "username" in your local working folder. Updates on the local file will be synchronized with the central Revit file first and it will attempt to update the file on the vault server. But since the file was locked by vault security setting, you will not be able to see the updates.
Regards,
Madhan
Can't find what you're looking for? Ask the community or share your knowledge.