Community
Vault Forum
Welcome to Autodesk’s Vault Forums. Share your knowledge, ask questions, and explore popular Vault topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Release a child assembly drawing where parent is used in a view for reference information

1 REPLY 1
Reply
Message 1 of 2
morbanTWYUB
64 Views, 1 Reply

Release a child assembly drawing where parent is used in a view for reference information

After searching on the forums for some time, I haven't found any posts about a situation like this. If someone has more information, please link in a reply.

 

We are trying to release sub assemblies and parts to manufacture while the main cell level assembly is still work in progress. To do this, our installers typically need to know where and how to install the sub assembly. We are providing this information in a drawing view of the sub assembly drawing that references the main cell level .ipn file. Is there a way to set the view, or the .ipn itself, as a reference only so we do not need to release the cell level files as "children" of their sub assembly drawing files?

 

For an example see the attached screenshot. In this example, the GFTX-BL3-PGL1.ipn belongs to the main cell level. Its child assembly is the one for which the drawing was made; A-02-010017. However, when we try to release the A-02-010017 drawing, it cites the GFTX-BL3-PGL1.ipn (and all of its respective child components) as a child assembly. This requires us to release the full cell model before we can release this drawing. 

morbanTWYUB_1-1690829750917.png

 

Is there a way to take a snip of the main cell or set it to reference so we can release lower level components with this information?

1 REPLY 1
Message 2 of 2

It's the chicken and the egg scenario indeed.
One way around this we used in a previous company was to derive (create simplified part) the main assembly, then right-click SUPPRESS the link of this reference feature, and include this part into a subassembly. That allows you to keep a reference of your upper assembly into your lower, and if you need to update you can unsuppress the link, update, then suppress again and save it, later updating the subassembly where this is used at.
We actually used shrinkwrap more and kept an LOD where all such references were not shown/suppressed from view. But nowadays I think derive and Model States might be the best way to go about it.

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report