-
Re: Get Latest Subassembly Overwrites Main Assembly
"Get Latest" will load the latest version of a file that's available from the vault into your computer's memory. Best practice is to get latest before checking anything out, that way you avoid the issues you're having.
Are you trying to work from an older version of the main assembly for a specific reason?
-
Re: Get Latest Subassembly Overwrites Main Assembly
I am typically working on the latest version of the top level assembly. Others will occasionally check in updated versions of subassemblies. When those come available, I try to incorporate them into the main assembly. If I'm only loading the subassembly, why does it reload the top level assembly? It should just update as if I made a change in the subassembly, not reload the archived version.
-
Re: Get Latest Subassembly Overwrites Main Assembly
Unless you don't have the latest version of the top-level assembly, or if you're doing a "get latest" on the top-level assembly itself, it shouldn't be reloading the top level. If you do a "get latest" on the top level when you have it checked out, even if you already have the latest version, it will try to load the most recent version from the vault, which means it will try to load the version that existed just prior to you checking it out (so it will ask you to either "save as" to preserve your changes, or to erase them by replacing the current model with the version from the vault).
This is why I typically "get latest" before I check out a file and before I've opened anything up in Solidworks. We've had too many headaches due to loading old versions of files - getting the latest version first helps reduce these headaches and prevents the issues you're seeing.
-
Re: Get Latest Subassembly Overwrites Main Assembly
I must not be clear.
- I have the top level assembly "A1" checked out and open, version "-/41" (editing version 41)
- I do a bunch of work within assembly "A1" and save many times.
- I choose "Get Latest" for a subassembly that a colleague has modified in the PDM Task Pane Tab
- Solidworks informs me I am editing version 0 of assembly "A1" and the latest version is 41
- Solidworks only gives me three options; "Use Version from Vault", "Save Open File as Copy" or "Cancel".
- If I select "Cancel" the old version from the vault is loaded anyway and I lose my work
- If I select "Use Version from Vault" the old version from the vault is loaded and I lose my work
- If I select "Save Open File as Copy" this will no longer be the same assembly!
I have no choices other than to lose the work I've done in the top level assembly if someone has updated a subassembly. How is this correct???
-
Re: Get Latest Subassembly Overwrites Main Assembly
Just for clarification, is this the type of message you're getting?
I think you may just have to save your changes and check in the top level assembly before getting the latest version of sub-assemblies. If I'm not mistaken, PDM will tie the current version of the top level assembly to the specific version the sub-components were at when the top level was checked out, that way if you "get" an archived version of the top level assembly it will also get the archived version of the sub-components that correspond to that exact version of the top level (if that makes sense). PDM can't associate two versions of a sub-assembly to one version of the top level.
Now that I think about it though, why it forces you to lose all of your changes instead of just replacing the referenced version of the sub-assembly is a mystery to me... I guess I've just gotten used to the quirks and have worked around them for so long that I forgot why I was doing that way in the first place.
-
-
-
-
Re: Get Latest Subassembly Overwrites Main Assembly
When your colleagues check in the subassembly after modifying it, You will have the older version attached in your main assembly. For updating that use PDM task pane to get the latest version of the modified subassembly, it will not ask you to save as parts of subassembly
-
Re: Get Latest Subassembly Overwrites Main Assembly
This does not work for me. See my response to Austin above.
If I "Get Latest Version" of the subassembly it will either reload the main assembly from the vault or ask me to do a Save As to the main assembly. Either way I lose all my work in the main assembly whenever I get the latest subassemblies!
-
Re: Get Latest Subassembly Overwrites Main Assembly
I don't recall the exact message, but when it asks you to use the version from the Vault do not cancel, select "NO" confirm each message this way.
-
Re: Get Latest Subassembly Overwrites Main Assembly
I just did this again a minute ago. The message only gives three options: "Use Version from Vault", "Save Open File as Copy" or "Cancel".
I am not given the option of continuing with my edits to the top level assembly. Getting latest of any subassembly forces me to lose edits to the top level assembly and revert to the version in the vault.
-
Re: Get Latest Subassembly Overwrites Main Assembly
When you get to the first message, hit ESC or cancel, now you will get the second message.
read the message carefully, make sure to select "No" only to the files that you know are newer on the Local Vault
-
Re: Get Latest Subassembly Overwrites Main Assembly
That SHOULD be the correct answer. However, The following happens:
- Selecting "No" will update the subassembly and retain my edits to the main assembly - BUT - when I later try to save the main assembly it brings up the "Save As" dialog box. It will not let me save the assembly because it says it is currently checked out. Yes, but TO ME! I now need to go to the PDM browser and Check In the main assembly, close it, open it back up and check it out again to continue working on it. I still lose all edits because I was not able to save.
- Selecting "Cancel" loads the new subassemby and the archived main assembly from the vault. It cancels nothing.
-
Re: Get Latest Subassembly Overwrites Main Assembly
I have seen the same behavior, i remember just checking in and back out the Subassembly it was complaining about.
-
Re: Get Latest Subassembly Overwrites Main Assembly
It will not let me save the assembly because it says it is currently checked out. Yes, but TO ME! I now need to go to the PDM browser and Check In the main assembly, close it, open it back up and check it out again to continue working on it. I still lose all edits because I was not able to save.
It can happen if you mix check in/out between SolidWorks and Windows Explorer. I think you should use only SolidWorks PDM Add-in to check in/out (only when document is open in SolidWorks).
And yes these message boxes are confusing. I think every user has experienced it.
-
Re: Get Latest Subassembly Overwrites Main Assembly
OK. I usually only use the PDM Add-in but when this happens I just have to close the file without saving - the Add-in won't let me check it in without saving. This forces me to use the PDM Browser in Windows where I can check in a file that is not saved.
-
-
-
-
-
-
