2 Replies Latest reply on May 10, 2012 2:51 PM by Gary Radish

    Tracking a Pack and Go

    K. Hampton

      Something we use a lot is Pack and Go to take a design and copy it to a new part number and alter it for another project.  My question:  Is there any way that you can take a part and find out what it was copied from.  I know that the PDM history does not give this information.

        • Re: Tracking a Pack and Go
          Benjamin Abshire

          You can use the check in with comment function in Copy Tree and include in the comment the source file (i.e. "Copied from Top Assy.slddrw") . Copy Tree is more useful than Pack and Go when dealing with Source and Destination folders inside the vault. I also find this function to be useful at quickly identifying files that can't be checked in because of workflow or duplicate file name restrictions. Also, if your library components are stored in a different folder structure other than your project folders, they are not automatically selected in Copy Tree.

          • Re: Tracking a Pack and Go
            Gary Radish

            Kyle you could probably create a variable and link it to data card.  Then if you do a pack and go you will have that previous filename variable in data card.  Then when you check-in you could list in comment field what you copied from and have it in your history.  Or probably could automate it with a dispatch script that could run during a workflow transition.

             

            Gary