SolidWorks PDM Standart is probable?
And if it is possible to describe process of relocation of files in more detail.
Files move manually? / automatically?
CheckIn, Workflow, Revizions is used?...
What settings at users / groups?
As I understood - users can work parallely. At the same time any of them can move files.
At this moment files of CheckIn?
After that other users perhaps will need to update local Cash and to receive the latests version (possibly manually).
There is an opportunity to set up Cash - it is possible to specify the necessary folders.
It is possible to update referenses manually.
Still there are settings of external references in Administration PDM and SolidWorks (what there settings?)
Toolbox is used? How it is set up? locally or in PDM?
Probably more initial information will not prevent.
is the assembly in your PDM vault also? and was it checked in after the part was added, but before the part was moved?
The assembly is in PDM vault. The assembly is checked when the user1 moves the parts, the problem is when user2 opens the assembly and the parts are supressed.
Thank you for your time.
are both users using (or at least have installed and turned on) the PDM add-in for SW?
I have had this problem many times. The way I understand it is:
- When you open an assembly SolidWorks looks in the assembly for the location of the individual files.
- SW then attempts to open the files from that location.
- If it doesn't find them it acts according to the option setting selected. Since SolidWorks made the Option in "Messages/Errors/Warnings" to automatically dismiss the reference update dialog after a short period of time -- and set it on by default, it is probably just defaulting to suppress the file.
I set all installations to have this turned off. I don't want the users to not know something was not found. It drives me insane that SolidWorks even created this option. It totally blows my mind that they force it on us. WHY DO THEY WANT PEOPLE TO HAVE BROKEN MODELS BY DEFAULT????? But, I regress, that is a different issue.
The main problem with SWPDM is that when you move a file (whichever way you do it) it does not open the assemblies and update the path saved in the assembly.
I would think that SW would be smart enough to know if you open a file from within PDM it should ask PDM where the file is before it tells the user to go find it or just suppresses it automatically.
If I have something wrong in my sum up please let me know as I would love to be able to move things around without having broken assemblies. The way it is, I just stop the process of moving hardware to the library and just leave the mess and nobody can find it so they just add another one.
I agree in each word Paul, how many people are you working with PDM?
We have over 600 users in different vaults around the world. Some of the vaults are large with hundreds of users listed in them. 2 or 3 have most of those users. The other vaults have 10 to 20 each. One of the vaults I have partner accounts from other companies so they can access the vault and work on projects using the classic web client.
I will try to specify more specifically.
1. How do files in the SolidWorks window (Pack and Go or Save As) or move to PDM (Move/Copy Tree or just dragging of files / folders) or somehow on another?
2. What means "when it fits with the assembly and it is OK" - All files rebuilded and saved in SolidWorks, and CheckIn in PDM (at the same time in the brief information on the entering details there are no warnings)?
3. Assemblies and details have some Status, Revision? The rights to move files is allowed for any Status?
4. The movement purpose - protection (blocking) against any changes or Library with a possibility of search, sharing and/or revisions or some other?
1- Most of times just dragging files. Folders are not allowed because PDM let you move folders even when you have in this folder a file thats is referenced in assembly that it is Checked Out by other user.
2- I mean, when the engineer checks that the part is OK in the assembly about dimensions.
3- Assemblies can have some revision, The rights to move files are allowed for all status.
4- Sorry, I don't understand this point.
Thank you Sam
Now something seems clear.
1. I suggest to try to add in settings of user / group in the section of the Menu - "move tree".
(If such opportunity in PDM Standart is).
Or try SolidWorks/move (in the shortcut menu - if SolidWorks Explorer is set).
Try to move something - what will be result and what warnings will be?
I have 2018...
and I get problems moved/editing files through the SW enviroment.....
SW will just crash without warning.
all folder manipulation has to be done through windows to get around this.
As I did not wait for any additional information, I tried to simulate as it is written and to move different files with different methods.
I long tried to repeat something similar, but it was impossible to me. I tried also "Pack and Go" and "Copy Tree" and Drag and drop both to Move a tree and to Move files (Solidworks Explorer) and just to copy the folder with files.
I did not find any problems on other computer.
Then I just moved only details to other folder (assembly remained on the place) - and received something similar to the asked question.
I am not sure that it becomes as I made.
In that case, in the local folder there are cached local files which need to be deleted.
After their deleting I did not find any problems.
If something does not work it is possible to try to update references manually in PDM.
It is possible to try to set up References in the SW and PDM settings - unfortunately I have no dc time' it to try.
It is possible to try to set up External references in SolidWorks and to add the "PARTS" folder to Referenced Documents location in SolidWorks and External references in Administration PDM.
But it is the best of all to use "Move tree" for relocation (a personal judgement, and I am not sure that it can be set up in the menu of the user in PDM Standart).
Try in SolidWorks in PDM tree - to update (refresh/renew *) tree and to use the version in vault.
It doesn't solve a problem?
(* - the note: I have no English interface now - perhaps the translation incorrect).