We have a situation where previously created non-vault assemblies need to be checked into vault. These assemblies need to find many parts that are now in vault libraries (unchanged). So we pull the assembly into the local workspace and open it using a vault project that is pointed to the vault libraries. But Inventor doesn't find the parts, we have to download the parts to the local workspace and browse to them to resolve the assembly. Why is this? One question, our vault library folders are not all top level, we have many folders below a single top level Libraries folder, is this a problem for any reason? Any input would be appreciated.
Vault Collaboration 2013 SP1
Dell Precision T3500, Xeon W3503 2.4GHz, AMD FirePro V4900
Windows 7 64-bit, 8 GB RAM
In the scenario you describe, I would do the below steps. It is a little labor intensive, but you are sure to get what you want when you run through the steps below.
- Once you copy the dataset to the local drive, identify what files are in “library” and what files are not, and remove the duplicate non library files.
- Get from Vault the necessary “library files” to your local workspace
- Open the assembly
- When prompted the files are not in local do you want to get from Vault choose no
- You should then be prompted to resolve the link for the files.
- Resolve the links to the new library location.
- Run the Rebuild All command with the assembly open.
- Save the assembly and update any drawings as necessary
- Check into Vault.
If the above doesn’t sound like an idea you would be happy doing, you can also use the replace components command with the assembly open.
- Open assembly with old files (non library files)
- Replace from Vault process
- Once all files have been replaced with Vaulted files, Rebuild All
- Check in
Data Management Support Specialist