2 Replies Latest reply on Mar 29, 2018 4:39 AM by Martien Mourits

    Automatically update drawings' referenced files

    Ruud Van Der Pasch

      Hello all,


      I've build a workflow wherein parts are being checked, released and approved. After approval the files are 'locked'. If we want to do a revision, this file is copied and renamed. We start with release 1 (R01). After a release some files need to be adjusted and therefore I managed to automatically copy the files with a new name (R02) and leave the R01 in the approved stage (Dispatch add-in). The referenced drawings are also copied and renamed to the new release. The problem is that the drawing (R02) is referenced to the earlier release (R01) of the part. Therefore I'm trying to find out if it's possible to automatically update the referenced file of the drawing. I want the drawing to be linked to the part with the same name (100001R01, 100001R02 etc). I know how to do this manually, but doing this every time we do a revision is a hassle. Maybe this can be added as a task to a transition in the workflow?


      I couldn't find anything useful with the Task Scheduler or using macro's, but maybe someone knows this better.


      Can someone help me out with this problem?


      If it's needed, we are using Solidworks 2016 SP5.0 and PDM Pro

        • Re: Automatically update drawings' referenced files
          Ctm Pdm Admin

          I don't know the answer to your question but I can tell that what you are trying to do is very bad practice and is working against the system.


          PDM already creates new version of files when they change states (or when users check them out and back in) and if they go through revision controlled states those versions are 'locked' and cannot be modified by default. So I don't know why you want to create new copies. Every file is already version controlled.


          • Re: Automatically update drawings' referenced files
            Martien Mourits

            Hi Ruud,


            What CTM Pdm Admin says is correct, this way of working removes the ability to easily look back at As Built situations as well. Best practice is to get rid of the revision in the filename and work with the versions and their corresponding revisions set through the workflow. There is no standard automated function in PDM to create the references as you requested, this can only be done by hand or (you probably guessed it) API.


            Is there any particular reason for this way of working? Maybe there is an alternative method that can also solve your problem altogether.