Why is it that the latest version of an assembly in the EPDM add in and in the search tool are not the same. Even after I clear my cache they come up the same as in the attached screenshot. From what I can tell the Bronze bushings in the assembly should not even show up when open in Solidworks.
Justin,
If you change the configuration setting on the Contains tab to @ you should see the bushings. The @ tab reports all components that are associated to an assembly, across all configurations.
Thanks for the response Charley,
How do I change the configuration setting on the Contains tab to @ in 2013?
Justin,
It's the <Do not show configurations> option in the configurations drop down:
That's what I thought. They still don't show up.
Justin,
Can you retrieve old versions in the Add-in ?
Yes I can. I've tried switching versions a few times. I just had my VAR look at it and they are also stumped.
Justin,
I've seen issues before with EPDM reading references from files with display states, can you save a copy of the assembly and purge all the display states and see if that helps. Are you having this issue with any other assemblies that have parts in your standard parts workflow?
There is only the default display state. This is the only one I know of that has an issue with parts from our standard library. I have seen instances where the assembly is not referencing the lastest version of one of the parts. It is hard to prove there is an issue in epdm since the user could have just not checked out the assembly and only the part. But in this instance it looks like the assembly was not checked out when the part was changed and the bearings some how ended up in the assembly. I found out that the user did a pack and go on this assembly. Not sure if this is helpful or not.
Justin,
Ah that probably explains what happened. When he used the pack and go the bushing was probably bundled with it and he dumped it along with the main part into a folder and checked it in. Then either you had the "Don't allow files with duplicate names" option turned on so he couldn't check in the bushing or he checked in the bushing and realized he didn't need it and deleted it. So when you open it in SolidWorks it uses the search routine to find a matching part in the vault so it shows up in the add-in, but there is no reference in the database because either the bushing never got checked in or the one it was referencing got deleted. If you check out the assembly and check it back in you should resolve this issue.
I think thats what happened. Thanks
Justin,
Ah that probably explains what happened. When he used the pack and go the bushing was probably bundled with it and he dumped it along with the main part into a folder and checked it in. Then either you had the "Don't allow files with duplicate names" option turned on so he couldn't check in the bushing or he checked in the bushing and realized he didn't need it and deleted it. So when you open it in SolidWorks it uses the search routine to find a matching part in the vault so it shows up in the add-in, but there is no reference in the database because either the bushing never got checked in or the one it was referencing got deleted. If you check out the assembly and check it back in you should resolve this issue.