When you checkin a standard part such as a washer or screw, into the vault - how to make this part as a standard part without rev. in the vault?
You can set up folders that contain parts that are not rev controlled in PDM Vault Admin.
I would also suggest that you search for some training (Solid Professor, I Get It, your VAR) to get a good basic handle on what the procedures are and what you can expect. Many people on the discussion forum are more than willing to provide some feedback but most are too busy to serve as teachers. Please don't misread this comment, but some help is better than others.
I understand everyone has a job to do but some tried to sneak in to read and anwser the questions. Their help is greatly appreciated; however, please don't feel obligated being here to answer all the questions. I've actually been getting help from my VAR, Hawk Ridge, but sometimes I got quick answer from here so hopefully, I was not considered as take advantage of it
For NON-revision controlled standard parts - such as the hardware items you refer to - we have a library folder structure on our network. Within the Vault Admin, we point to these network folders as libraries on the Standard Library tab.
When you check in an assembly that contains model items located in these libraries, PDM recognizes that and does NOT check those files into the vault. Instead, it places a shortcut icon representing the hardware file into the vault view.
So the library files are never actually checked in, but the vault knows they are part of the model, points to them, and when you check an assembly out of the vault the references to them are intact.
I'm jus wondering what happens if you check out the assembly which is linked to some standard parts and work offline on the field. Do you have to copy these standard pars to your local drive and point the link to it
Not something I have ever done - all our work is in-office.
Someone else will need to chime in on how they handle this.
My inclination is that grabbing the standard parts and re-pointing references would be a nightmare. Pack-n-Go would capture all easily going into the field. But I have no idea how you re-integrate the field-modified assembly back into the office workflow.
PackNGo is the excellent tool we used for a long time to grab a whole assembly to the laptop whenever we worked on the field (off line some time) with customers. I thought there migh be another way to handle this with PDMw
I created a folder for hardware and use PDMAdim to point to it as a standard lib. w/ disable check in of documents checked; Howver, when I check in the part, rev. still shown on these hardware parts - Do I have to do anything when I check in
That sounds like how I have ours set up - my setup is shown in the image in above post.
Just confirmed - in our vault for library items the revision property is shown as... <Not Revision Managed>
Within your assembly, the referenced path to the hardware is the library folder? If they are not brought in to the assembly from the folders listed as libraries in your Workgroup Admin, WPDM will consider them regular parts.
This it totall werid. I'm still testing the PDMw now so I set the Vault in my local C and working folder in local D
In the VaultAdmin, if I link the the standard libraries to a local folder in C, then it works; however, if I link to a folder on the server, then Vault check in the standard parts as a regular part with rev. controlled. it drives me nut !!!
You might have a permissions issue with your network share area. You might also make sure your mapping to your libraries in the Vault Admin is a full path and not a mapped drive letter. SW can be goofy with mapped drives sometimes.
Retrieving data ...