4 Replies Latest reply on Apr 26, 2017 4:21 PM by Craig Schultz

    inserting parts/assemblies into vault (pdm standard)

    Gordon Rigg

      Right, I have a vault set up, I am a user with access to the vault, I have some data cards and a workflow and all that (I'll soon find out how badly I've done that bit, but I'm not working with any real data and I can easily start again from scratch with more understanding )

      Now I have some questions:

      • I'm wondering how to get round a problem with the toolbox, or if it is a problem that might make it difficult to run workgroup PDM and PDM standard at the same time, because its nagging me to put my toolbox files into the PDM standard vault...what is the best way forward on that? I expect to run WGPDM and PDM standard in parallel for a long time gradually moving stuff into PDM standard.

       

      • How do I insert an assembly and all its referenced components into the vault from  external windows directory(s) in one go? when I drag and drop an assembly it just brings the one file, leaving warnings that it links to external files. surely there is a way to make it bring all its references with it like WGPDM always did so easily?!

      Why does it just put the assembly in there with non functional links without offering me the option to bring all the referenced files too? that seems very very poor...I'm obviously missing something (unless PDM standard is a truly awful crippled piece of junk?  )

       

      • Opening, checking that one assembly out in solidworks doesn't seem to offer any extra functionality compared to windows explorer...I'm seeing a lot of grey and disabled stuff there (but not all so it is communicating with the vault) - I guess its just because I have only one assembly in the vault without its components!

       

      I've found a lot of helpful information on setting up PDM standard on line, but the actual user operation info seems to be lacking. The user information seems to assume a full set of data already in the vault and any new files are created in the vault (fine for the 0.001% that are starting from scratch).

      How to get data from a windows file system into the vault easily? (never mind out of WPDM!)

        • Re: inserting parts/assemblies into vault (pdm standard)
          Wayne Marshall

          Hi Gordon,

           

          Take a look at this webcast as it may give you some pointers.

           

          Handling Legacy Data in PDM Standard

           

          As you have found, there is no 'Bulk Upload' tool for PDM Standard but the 'Update References' tool may help you manage how you import the Parts / Sub-assemblies after dragging in an Assembly (Note if you have already Checked the file in once you will need to check it out and change 'something' e.g. a value on the DataCard  - for it to re-inspect the references)

           

          Also worth commenting that if you plan to work with both systems side by side that you should disable the WPDM Add-in when working with files in PDM Standard. WPDM will force those files to be Read Only even though they are checked out in PDM Standard - which can be confusing!

           

          Regarding Toolbox. PDM Standard (and Pro) require that the Toolbox / Standard library's are added to the Vault IF you want those items to appear in the Contains / BOM tabs, so you may need to duplicate the Toolbox putting a copy in PDM and configuring the admin tool accordingly, whilst evaluating how you will use PDM Standard.

           

          Kind regards

           

          Wayne

            • Re: inserting parts/assemblies into vault (pdm standard)
              Gordon Rigg

              some more questions:

              The advice is to put the PDM standard working parts directory on C: root. I have two hard discs in each machine and we put the WGPDM working directories on the seconds disc at the root of that. Would it be just as good there? or is there a good reason to put it on C: with the program files?

                • Re: inserting parts/assemblies into vault (pdm standard)
                  Jeff Sweeney

                  Assuming the local drives are the same speed and equivalent disk space, there really isn't much of a technical advantage of the location you put your PDM local cache.

                   

                  I do like to keep the local cache as shallow in the folder structure as possible. Long path names (more than 255 characters) is bad, plus I like typing more than using a mouse -shorter paths is better.

                   

                  If you think you will be putting together internal training documents, I like to be consistent so your training materials do not confuse new users. i.e. "Hey why is my vault on the d:\ but the training materials say c:\?!"

              • Re: inserting parts/assemblies into vault (pdm standard)
                Craig Schultz

                How do I insert an assembly and all its referenced components into the vault from  external windows directory(s) in one go?

                 

                Are all your parts/drawings in the assembly in the same directory?  If yes, just grab them all and drag away......  If not, do a save as with the references and point it into the vault.  In both cases I would suggest dragging/pointing them into a "sandbox" folder where you can check in, make sure the references are there, and move to appropriate folders afterwards.

                 

                The advice is to put the PDM standard working parts directory on C: root.

                 

                 

                This is the easiest way to do it.  I have learned (the hard way) to set up as C:\Vault Views as my root.  That way if you need to reconnect to the vault, you can drag the old folder (not the blue swirl) into C:\Vault Views\Old Views.  Also keeping it to C;|Vault Views\<vault> it's easy to set up other clients with the same folder mapping/structure.  Last place I was at, pre-ePDM, another guy thought there was no issue with him mapping the folders to drive letters that "made more sense" to him.  What a PITA when work over the network.