this started happening when we started using the vault. now it happens on my hard drive.
this started happening when we started using the vault. now it happens on my hard drive.
What's your exact workflow for insert the sub-assembly?
Do you get different behaviour if you:
Or;
Dave Laban wrote:
What's your exact workflow for insert the sub-assembly?
Do you get different behaviour if you:
- Open sub-assembly so it works, then go File > Make Assembly from Assembly, save this new top assembly, close and re-open.
Or;
- Open sub-assembly so it works first, then go to your existing top assembly the go Insert > Component > Existing
Either way depending on how development occurs. Either way should not yield missing files AT ALL.
Items that are saved to the C Drive, but not added to the vault will not be able to be searched using the PDM search tool. You will have to navigate to the folder location and check to see if it is grayed out (not actually added to the vault). One thing to check if you are not the only user of an assembly is specifically going to the folder location of the "missing" item (file) and make sure it was actually added to the vault. If the file does not exist, then either you are the user who created the file needs to add it to the vault (you will have to if you are the one who did not add it to the vault. ALSO, the not adding files to the vault when saving into the vault folder location is an issue that is usually caused by network hiccup.
OK, if I open the sub assembly first, then the top assembly, everything is good, I save the top and re-open and it looks ok. I just hope it stays that way. also I don't know why this happens. the bad sub is the same as the good one, same file location, same assembly. it seems that something in the top assembly is doing this.
Scott Cole
Could you upload screen shots..
Are these Virtual Parts?
No idea on the PDM, but are the parts checked in ?