AnsweredAssumed Answered

Workgroup PDM Change Library Locations - How to recognize library parts?

Question asked by Daen Hendrickson on Apr 17, 2017
Latest reply on Apr 21, 2017 by Christian Chu

Like • Show 0 Likes0
Comment • 6

We are using SW2014 SP5.

First some background:

Our SW installation was at a previous company. Individual workstations. PDM Workgroup on a server. Libraries on a shared area of the network.

After that company closed its doors, one of the principals launched the current company and transferred the SW assets. However, in the beginning the entire PDM Workgroup installation was placed on a desktop since no servers were in place.

Fast forward several months and servers along with a proper network were installed. The design libraries were moved (actually just copied) from the desktop to a network share area. The PDM installation was still run from the desktop. And more pressing crises sidelined any additional work.

Fast forward to last week when a little digging re-exposed that the PDM Vault Admin settings were still pointing to the libraries on the desktop, not the libraries on the server. This would help explain why on check-in all our new library parts keep trying to be saved in the vault.

Friday afternoon I added paths to the network version of our libraries and restarted the vault with validation and vault rebuild turned on. This morning, in my SolidWorks Vault View I can see the newly added libraries, but they show no parts. I don't want to delete the links to the desktop libraries (CAD3-PC) until I have the network libraries working. How do I get the parts to show up in the new libraries?

Thanks,

Daen

Daen Hendrickson Apr 17, 2017 1:19 PM

Correct Answer

And I think I have the answer...

I checked in an assembly to the vault. With that check in the newly added network libraries gained components. Only the components associated with the assembly, but they are becoming populated.

Any thoughts if now deleting the old links to the desktop would "break" anything? I am thinking the paths to the library parts inside the assembly files are pointed to the correct networked libraries. And if not, you will be prompted to find the missing file (which we still get on really old files that have not been updated since at the previous company).

Daen

See the reply in context

No one else had this question

Outcomes

Christian Chu Apr 17, 2017 11:49 AM

Daen,

can you post a screenshot of your PDM Vault-Admin here ?

and by the way, are you sure there are some parts in the folders such as "Design Library - ISTS"

Actions

Daen Hendrickson @ Christian Chu on Apr 17, 2017 1:13 PM

Christian,

Here are some screen shots.

Additionally, yes I am confident that there are files in all of the "Design Library - xxxx" paths. Part of the reason this hasn't appeared grossly problematic is that the libraries came filled from the old company when placed on the new company desktop. Then when they were copied to the network shared area only newly created library items don't match. Regarding the local desktop (CAD3-PC) Design Library - SolidWorks not showing any files in the screenshot above, they never saw a use and didn't install. It contains all the sample stuff that installs with the SolidWorks installation and is there for training. When we created the network copy of the libraries, I restored this library.

Daen

Actions

Daen Hendrickson @ Daen Hendrickson on Apr 17, 2017 1:19 PM

And I think I have the answer...

I checked in an assembly to the vault. With that check in the newly added network libraries gained components. Only the components associated with the assembly, but they are becoming populated.

Daen

Actions

Christian Chu @ Daen Hendrickson on Apr 17, 2017 1:27 PM

Daen,

In the Standard Libraries tab, what you see in the listbox is just a link, you can delete/relink without any harm to your Vault

Depend much on how much comfortable you want to do this but I recommend you backup all the design library folders and create a new set of design library folders

Delete all the link in the list and relink to the new set of design library folders

Actions

Daen Hendrickson Apr 20, 2017 8:04 PM

Just as a follow up... I checked in a completely new assembly today. ALL of the library parts were recognized as such - the check-in popup dialog did not require a single edit / deselection of incorrectly selected library parts!

The other benefit is that the time for the check in process from mouse click to filled dialog dropped from a typical 45-60 seconds for an assembly of this size to just a few seconds - way under 10! Iz Goot!

Daen

Actions

Christian Chu @ Daen Hendrickson on Apr 21, 2017 12:12 AM

Glad to hear that

If you do the setup right in the VaultAdmin, then you never have to worry about the lib. part checked-in the Vault

Actions

6 Replies

Christian Chu Apr 17, 2017 11:49 AM
Mark Correct
Correct Answer
Daen,
can you post a screenshot of your PDM Vault-Admin here ?
and by the way, are you sure there are some parts in the folders such as "Design Library - ISTS"
Like • Show 0 Likes0
Actions
- Daen Hendrickson @ Christian Chu on Apr 17, 2017 1:13 PM
  Mark Correct
  Correct Answer
  Christian,
  
  Here are some screen shots.
  
  Additionally, yes I am confident that there are files in all of the "Design Library - xxxx" paths. Part of the reason this hasn't appeared grossly problematic is that the libraries came filled from the old company when placed on the new company desktop. Then when they were copied to the network shared area only newly created library items don't match. Regarding the local desktop (CAD3-PC) Design Library - SolidWorks not showing any files in the screenshot above, they never saw a use and didn't install. It contains all the sample stuff that installs with the SolidWorks installation and is there for training. When we created the network copy of the libraries, I restored this library.
  
  Daen
  Like • Show 1 Like1
  Actions
  - Daen Hendrickson @ Daen Hendrickson on Apr 17, 2017 1:19 PM
    Unmark Correct
    Correct Answer
    And I think I have the answer...
    
    I checked in an assembly to the vault. With that check in the newly added network libraries gained components. Only the components associated with the assembly, but they are becoming populated.
    
    Any thoughts if now deleting the old links to the desktop would "break" anything? I am thinking the paths to the library parts inside the assembly files are pointed to the correct networked libraries. And if not, you will be prompted to find the missing file (which we still get on really old files that have not been updated since at the previous company).
    
    Daen
    Like • Show 2 Likes2
    Actions
  - Christian Chu @ Daen Hendrickson on Apr 17, 2017 1:27 PM
    Mark Correct
    Correct Answer
    Daen,
    In the Standard Libraries tab, what you see in the listbox is just a link, you can delete/relink without any harm to your Vault
    Depend much on how much comfortable you want to do this but I recommend you backup all the design library folders and create a new set of design library folders
    Delete all the link in the list and relink to the new set of design library folders
    Like • Show 1 Like1
    Actions
Daen Hendrickson Apr 20, 2017 8:04 PM
Mark Correct
Correct Answer
Just as a follow up... I checked in a completely new assembly today. ALL of the library parts were recognized as such - the check-in popup dialog did not require a single edit / deselection of incorrectly selected library parts!

The other benefit is that the time for the check in process from mouse click to filled dialog dropped from a typical 45-60 seconds for an assembly of this size to just a few seconds - way under 10! Iz Goot!

Daen
Like • Show 1 Like1
Actions
- Christian Chu @ Daen Hendrickson on Apr 21, 2017 12:12 AM
  Mark Correct
  Correct Answer
  Glad to hear that
  If you do the setup right in the VaultAdmin, then you never have to worry about the lib. part checked-in the Vault
  Like • Show 0 Likes0
  Actions

Workgroup PDM Change Library Locations - How to recognize library parts?

Outcomes

Related Content

Recommended Content