Where Used Tab doesn't show component's related assemblies.

first thing to check would be are you looking the at the where used for "all versions"?

Remember that SolidWorks Explorer reads the "file references" directly from file.

EPDM only read the meta data that is stored in the SQL database.

Depending on how the assembly files were checked-in could control the information that is shown.

If you check-in the assembly from SolidWorks, the where used references get updated accordingly.

If you check-in the assembly from Explorer, you may not/will not get all of the where used references.

I'm having issues where "Where Used" shows something on my screen, but doesn't show the same things on my colleague's screen.  All the files have been checked in. 

I've also been really suspicious of EPDM's "Where Used" being very inaccurate.  However I don't have SW Explorer installed, so I'm really in the dark and don't trust it.

Hi Everyone.

I work for a VAR and work specifically with EPDM. Let me just state the following:

The references in EPDM and SWE (WPDM for that matter) should always match.

The mechanism for establishing the references between files is triggered whenever a file is checked in. SolidWorks reads the file references from the file header and writes the information to SQL for fast retrieval. Therefore, if you checkin an assembly inside of EPDM (using either the vault view or SW Task pane), the references for that file will be created for all files in the vault that exist at that time, linked to the assembly...i.e. if you check in an assembly (with missing references) and later check in an individual part file, that part file will not show as 'where used' until you have (as a minimum) opened, rebuilt, saved, and checked in the assembly to update the references for all its children

As stated earlier, it would be unacceptable if the references were not read consistently, and I can assure you this is not the case.

To make life easier for the end user, the specific version of a file shows its 'where used' information in the where-used tab, so that you don't have to manually search all the links yourself, but should you need to, then the 'all versions' setting will let you peruse all the possible combinations for the different versions of assemblies that this file belonged to. So if v1 of assembly 1 contains no reference to this file, and then v2 onwards of the assembly does contain a ref to this file, then the 'all versions' setting will reflect this accordingly by displaying the version number of the assembly at which this component was inserted. It will not display old references, only the newer insertions. I would encourage you to test this with a 2 part assembly, first inserting the 1 component, checking in the assy, then the 2nd component, checkin, then checking the where used tab for the first component

That being said, if the 'all versions' setting doesn't work it means 1 of 2 things:

• The reference was never established (i.e. the assembly was never checked in after the rebuild)
• The file was copied into the vault after the assembly was initially checked in. To fix- checkout - rebuild - save - check in