External link refence problem on sketch during a pack and go

Hello

I am in the design phase of a parameterized assembly and with external references in my sketches, various sketches of various parts are based on a general skeleton. everything works. My problem is that this assembly is to be modified after a pack and go, and that when I create my second assembly, with pack and go and by modifying the names (adding serial number for example) it loses all my external references in my sketches, equations and function it's ok, but in the sketches it keeps the link with the old part and necessarily any bugs. How do I make sure that the pack and go doesn't also change the Sketch Links? I'm not going to recreate all the links by hand every time.
image
I put an image to show you I don't know if it will work it's the first time I've used the forum.
Thank you in advance for your return.

Hello and welcome;

It would be necessary to specify the Solidworks version used (the pack & Go does not malfunction in the same way depending on the version).

You should also look at the Solidworks System options in " External References ":
image

Depending on the settings chosen here, Solidworks will handle external references defamably.
(be careful, these are my settings... We have banned the use of external references in our company, so the above options will not necessarily be relevant in your case...).

Kind regards.

1 Like

Hello, thank you for your feedback, I'm in SW 2024 SP3. Yes, the use of external references is complicated but I don't see how to do it without it when it comes to configurable models (apart from driveWorks). Thank you, I'll look at this side if I find any interesting things.

Hello

We work with external references and virtual parts.
However, we limit them to ONE level: the virtual part refers to the non-virtual assembly of the top and end point.
If you start to have external references on several levels, it's quickly unmanageable.
The virtualization of the parts was largely done to avoid the problem of external references to the wrong file if the pack&go is done incorrectly.

Hello, Yes this is my case I work with external references on 4 levels, your idea is not bad to have only a real assembly and to work with virtual sub-assemblies/parts the problem and that behind to make my orders and production management we need a real SLDPRT file, it's not just a 3D visualization but a 3D on which fab plans will be based, laser etc. and pack and go doesn't seem to be able to follow up on external references (or maybe only on one level...)