1 Reply Latest reply on Sep 21, 2010 7:56 AM by Lucas Dexter

    Adding legacy files to vault at current revision

    Lucas Dexter


                I know this has been asked in the past but I want to pose this question again and hopefully get some examples how to resolve it.  We are preparing to add many legacy files into our already established vault.  These legacy files have a revision variable used to specify the revision in the drawing and ultimately in the data card.  I would like to be able to pull the revision variable value and use it to change the EPDM revision upon checking the file into the vault.  This will eleviate the need for the file to go through some sort of "Revision" workflow manually which we utilize for files that are already in the vault.


                I have heard from several EPDM admins, programmers, users, etc. there is now a method in the API that will allow the revision variable to be used for this purpose.  Is there any way someone out there can give at least a hint as to how to go about this?  The issue is, I understand programming concepts but I am not a programmer.  I am doing research for one of our programmers so he can write some sort of add-in with the API to resolve our legacy file revision dilemma.

                There are a couple unknowns we are dealing with:


      1) Which method to use to grab the variable value

      2) Which method to use to change the EPDM revision

      3) Which variable in the database represents the EPDM revision


      The overall concept seems pretty straight forward.  Once we know these things I think we will have a better chance at creating the program.


      Any help is appreciated.




        • Re: Adding legacy files to vault at current revision
          Frank Pampreen



          We have written a migration tool that is designed to do this for our customers legacy migrations.  It is designed around getting legacy data from some windows location as opposed to some other legacy document control system. It uses wild character pattern matching in the filename to extract out a revision value and part number.  It can also use SW custom properties if some legacy files have it and others don’t.  It has an option to have the revision driven by the drawing or the part.  For example if the part and a custom property of revision but the drawing has a revision in the name than we can set a priority for which one should be the correct revision.  If you are interested in it I would be glad to show it to you.   



          Frank Pampreen

          CAP INC