Why is Pack & Go is pulling upstream files?

[Mike Gera]

I'm having an issue where Pack & Go sometimes wants to pull in "upsteam" files. In the example below, I executed a Pack & Go on 8546-03_REV_A.SLDPRT.

Despite the fact that 8546-03_REV_A.SLDPRT is part of as8546-03_REV_A.SLDASM, only 8546-03_REV_A.SLDPRT and 8546-03_REV_A.SLDDRW should be part of this Pack & Go.

So I have something set wrong, perhaps?

Thanks for any replies.

[Dwight]

Check to see if a component of your low-level assembly is also a subject of a view in a higher-level drawing. If the higher-level drawing has one view with that component as a subject, then it assumes that the higher-level drawing is a drawing *of* that component and needs to be included in the pack'n'go, because you requested the drawings. And because it included the higher-level drawing, it had to include all the part and assemblies shown in that drawing.

We have a label that goes on all our instruments. Most of our top-level assembly drawings used to include a view of just that label, instead of a view of the instrument in which the label appeared. Because of this, any pack'n'go of an instrument with drawings checked used to include all our instruments.

Dwight

[TTevolve]

If I want to have the drawing in the pack-N-go I start the pack-N-go from the drawing, not from the part or assembly. I leave the include drawings unchecked, but if you start the pack-N-go from the drawing it still includes it.

Do you maybe have some in context relationship in the assembly as why it might be pulling that, or it could be that assembly has views in the drawing possibly.