You can overcome this problem by turning off the global setting for users " Always work with latest versions" and enabling allow users to work with version on the folder persmissions.
This ensures that, It opens up the version of the file as used in the assembly.
Hope this helps !
Thank you very much for the info. I've been testing many things these days after you told me this.
I'm searching for the best solutions to treat our designs.
As Raghavendra eluded to, you may have the setting always work with the latest on. Let's assume for a minute that you don't. ePDM will allow you to either show the version of the file "as it was built and saved" or "with the latest version that had the reference in the assembly". It is easy for users to get the wrong versions of file(s) if they are not careful or properly trained. Every assembly on check-in stores an "as-built" type snapshot with the exact versions and even configuration that were in that assembly of the parts and versions on based on what was in your local cache on that check-ins. So ePDM will be able to show you the configuration as it was when saved. Things get more confusing when the common library part may have "configurations" (e.g. different lengths driving different part numbers and configurations in the part file itself). From purely a PDM standpoint I prefer not to have those types of configurations as they should really be different standalone files. It makes doing where used and contains easier to navigate. I have no problem of configurations in ePDM if they are for different display states or "open / closed" options of a single file/part number.
You're right with everything you talk about.
I agree with you that configurations are better treated if we use standalone files.
Thank you, continue trying.