I made a test in EPDM 2014 and it works well even parent assembly is checkout and when I opened the parent assembly there are no messages ref. renamed component.
I don't made a test when there are different users on different computers.
As I expected there are problems when parent assembly is open in SW.
How do you rename the child assembly - right click rename?
Thanks for testing. What I did to simulate our working environment was:
1) Open top level assembly and check out on machine one.
2) On machine two go into vault view in Windows explorer and rename component
3) Go back to machine one, save the file in Solidworks and try to check in. Assembly is saved with component with original name and check in gives error that component with original file name is outside of the vault. This means the user then has to replace the component with the new name from the vault
I since went back and tried the same thing but without the assembly file open in Solidworks on machine 1 when I do the rename and I get the same results. As long as the top level assembly is checked out, the references are not updated when the component is renamed.
This is a major issue for us because we started with all descriptive file names so no we need to go back and a large number our files with the correct part numbers. I guess we'll have to have everyone check everything in and find other things to do while we rename them all. Disappointing - not really what I expected from an Enterprise level system...
I have definitely found it to be true that the parent should not be checked out when renaming components. The exception seems to be if assembly is checked-out by the person that does the rename.
As far as your team - I can see how that is a hassle. On one hand renaming when other people are working on something should not be taken lightly. But you are right that it would be nice if EPDM could handle this. I'm trying to get users in the habit of not leaving anything checked-out overnight. If you do something like that, at least for the weekend, then someone could do a mass rename in the evening.
Abby, Always rename when both component and Parent are CheckIn... not sure if that is written anywhere but I find that this prevents any issues with lost references.
I see potential errors if you have multiple persons working an a same large assembly for example. Person A is having the main assembly checked out and mayby couple of sub components. Person B takes one sub assembly and renames the sub assembly + components, checks them in... Now Person A checks the main assembly in (without updating it, without knowing persons B actions)... So the main assembly references are to local cached old named components...
I have not tested this, but I would gather this would generate some confusion on both ends (software/user)
So I would assume, that one person making the components re-naming is OK, but with multiple persons you need to be careful with local caches etc.
Please do share your findings.
The parent file must be checked in so that EPDM can update the path to the reference file with the new name. Doing this while the file is checked out could result in lost work done to the file since it was checked out. If you want an in depth understanding on how EPDM handles this and other file reference related topics view the SolidWorks World 2014 session "How SOLIDWORKS Enterprise PDM Manages CAD References" by Tor Iveroth.