We have transferred data from our Swiss company PDM vault and would like to translate folder names from German into English. Is there an easy way to do this without messing up paths?
Jeremy is correct. The only thing to be aware of is that all the files in the folder must be checked in. And any files referencing them must be checked in as well. This is necessary for PDM to modify the reference paths in the files.
you should be able to freely rename folders (and files too) - the file references for SW files inside of the vault are stored in the database, and it keeps track of the changes.
Like Jeremy and Michael suggested you can rename freely names of files, and directories inside the Vault. EPDM keeps track of all changes, and updates references on all files that are checked in. If you can ask your users to check all files in before renaming files/folders. Or at least the ones that are related (referenced) to the file/folder that is been renamed.
Thanks for the replies. We will try this! It's very scary considering SolidWorks generally won't work that way, but that would be great if this can be done. Thanks again!
It is scary I have to admit... We have been using SW for years, but EPDM is a new thing in our company, so all users are a bit scared and every time they see a warning or a new message they think that something went wrong:) I find it funny, but I like challenges, and I enjoy this! Good luck with your Vault... we all need it:)
There is one thing you need to always remember when renaming or moving files in the vault. When you open a SolidWorks assembly it looks at its internal table to find the included parts and sub-assemblies. When you change a file/folder name or move something EPDM does not modify the relative path in the referencing assembly files. So, you end up with missing files when assemblies are opened.
It can be very frustrating for users when all of the sudden everything is broken. I am not trying to deter you from renaming, just do some tests on some small folders before you go hog wild on the whole vault.
Actually EPDM should modify the paths of the external references in the SolidWorks assembly file. This is why the referencing files must be checked in.
Your right - It should modify it, but it doesn't.
We moved a couple hundred library type files last summer from project folders into the library. We had people all over the place complaining about missing files in their assemblies that worked correctly the last time they opened it. Move Tree and Copy Tree don't modify the parent files they just move the files you are telling them to move. Copy/Paste also does not modify external references in the files. I have actually verified this with SolidWorks. Unless, I was explaining my issue in correctly to them or misunderstood what they told me.
When a file is in EPDM it should not matter if the parent is checked out or not. SolidWorks should always get the external reference path from PDM and not the internal path. SWPDM is the Data Manager not the individual files that don't have any way of checking themselves for correct external paths.
Once we've added files with correct references and checked them in, we've never had a problem with broken references when moving or renaming SolidWorks files in a vault.
While I think I understand your point, requiring a SolidWorks file to use references stored in the vault database would make the file dependent on the PDM system. That would fundamentally change the way SolidWorks operates. Many SolidWorks users do not have PDM. Also, since SolidWorks 3D existed before PDM, PDM was designed to work with it.
you mention copy paste, copy tree, and move tree - I've never used any of those in our vault.
dragging the file from one folder to another in the explorer view has worked perfectly for maintaining references for us.
Retrieving data ...