I'm opening assemblies that other people have made in EPDM, and many of the assemblies come in with errors. I have gotten the latest version of everything and cleared my cache, but I still get this message the "reference file is of older version." I believe this is the reason that the assemblies have issues that I am opening, but I can't figure out how to get the latest version of these assembly files. I've attached an image for reference.
Hey Patrick,
This is just a warning that a part has changed since the last time it's parent assembly has been checked in. It may very well be open with the latest version but to get the error to go away you have to check the assembly out and back in (it might be a sub-assembly, to get rid of this you need to check out every assembly that's a parent of the older version file). That being said I doubt that's what's causing your errors.
Hi,
Is in Solidworks PDM 2016 this solved, can i by checking in a lover rank part automatically update all assemblies that are referenced by that part or i need to do it for every assembly manual one by one? Or is there a another way to do this ?
You cannot get rid of them without checking out the assembly with the out of date child part, saving the assembly with the up to date part, and checking it back in. You will need to start at the lowest level of the assembly with out of date references and work your way to the top to get rid of them all. Its painful.
I know that and i am working that way, but is there a way to automatically check out all referenced assembly and subassembly and drawings what need to be check out and check in referencing to that part?
No, but that would be really neat. Then again, and I haven't had the time to play much with this, but i guess the new "version overwrite" feature in PDM 2017 will also help with this problem. I mean it all depends on the engineering change process, but i can easily see this will help out in these kinds of situations. Unless there is a major change, maybe even a revision, you just overwrite existing version, so the version reference tree is maintained and without warnings. Just be careful, it really does overwrite, there is no going back, except backups.
It still seems like a good idea. Perhaps someone should make this an enhancement request, where a company can select whether to update version reference tree or not upon check-in of a sub part or assembly.
We are working with assembly over 2k parts( subassembly and parts combined..) Our main assembly has many components like glass, electro components, engine parts... that are not changing often but we change basic sheet metal parts and assemblies that affect main assembley and then it is a pain to recheck them all. My VAR says that he can help me with SolidWorks questions but he would not help me with a standard PDM... And most things are hard to find on internet and books are not a real big help when u need to work and learn in the same time... Hope it gets easier, more work and less search.
I would love to learn more about how people work with changes in large assemblies in PDM.
Bottom up updating, is that the only way? And can it be done simple?
I think it's related to the topic, but please let me know if you think i'm hijacking this thread.
At first I to was concerned about this. The small yellow circle/exclamation point makes the perfectionist in me cringe. Then I realized that if the change does not effect the geometry, (like a properties update to correct spelling, a material was forgotten, or something low level) then it really does not matter - which is %99 of the time. What I struggle more with is that out of date references can come up to date by passing the assembly through a transition that contains an action. We use a few logical branches in our workflow to control a few variables and sometime an out of date part will get updated and sometimes not depending which part of the logical branch it flows through, and weather that branch contains an action. Most the time it does not matter - but those circles are painful for my ego... I am looking forward to version overwrite!
While this tool exists it is a pain to run this for every out of date assembly in the database, and if you ask any VAR they will warn you against over use of this tool. It is intended for migration between software versions on a large scale basis, not day to day use... although it does work.
Hey Patrick,
This is just a warning that a part has changed since the last time it's parent assembly has been checked in. It may very well be open with the latest version but to get the error to go away you have to check the assembly out and back in (it might be a sub-assembly, to get rid of this you need to check out every assembly that's a parent of the older version file). That being said I doubt that's what's causing your errors.