I want a simplified answer to share to our users,
What's the difference between copy tree and pack and go in EPDM?
thanks
Dwayne
I want a simplified answer to share to our users,
What's the difference between copy tree and pack and go in EPDM?
thanks
Dwayne
Thank-you Charley! appreciate the answer is there any reason to consider using Pack and Go in EPDM if Copy tree does a little more? Thanks again sir.
If I recall correctly, Pack n Go will not cache child documents so it may not work correctly. Or it may copy older cached versions. We instruct everyone to always use Copy Tree from within PDM.
I really wish they would consolidate the two tools though into one that can recognize whether its in the vault or not......and just call it one thing like "Copy with references".
Charley Saint wrote:
Hey Dwayne,
They are pretty identical, but Copy Tree adds some EPDM functionality. For instance you can bundle the latest versions of parts of an assembly or you can get the "As Built" version which is the versions associated with that version of the assembly. You can also regenerate serial numbers if it's getting copied into the vault and check-in after copied.
Plus a ton of functionality for cloning drawings and maintaining the link to the models, even if the names and/or locations are changed.
Dwayne Parrott wrote:
I want a simplified answer to share to our users,
What's the difference between copy tree and pack and go in EPDM?
thanks
Dwayne
Read this for an in-depth comparison:
http://www.javelin-tech.com/blog/2016/05/pack-go-vs-copy-tree-solidworks-pdm/
Hey Dwayne,
They are pretty identical, but Copy Tree adds some EPDM functionality. For instance you can bundle the latest versions of parts of an assembly or you can get the "As Built" version which is the versions associated with that version of the assembly. You can also regenerate serial numbers if it's getting copied into the vault and check-in after copied.