I'd like to run a scenario by everyone, which seems to work but doesn't seem to match Inventor's desired structure of things.
Let's say we have a top level assembly, "FirstAssy.asm", that calls up multiple assemblies such as "SecondAssy.asm", who in turn call up parts such as "Parts.ipt"
- SecondAssy.asm has multiple view representations that each turn on/off the visibility of multiple Parts.ipt to show different configurations of SecondAssy shown on drawings
- FirstAssy.asm has the same named view representations that each call up a particular view representation of SecondAssy to provide different configurations of FirstAssy.
When in FirstAssy I have been doing this by creating the named view rep, then Right Clicking on SecondAssy.asm -> selecting Representation... -> then under the "Design View Representation" pull down changing the view rep from Master to the desired named view rep in SecondAssy.asm.
This seems logical to me, and seems to work. However, if you were to right click on SecondAssy again and go to Representation... the Design View Representation still shows as Master, even though it's not. This tells me that this Design View rep hierarchy would not be clear to someone not familiar with FirstAssy.asm.
The second thing that leads me to believe that I might be bypassing Inventor's desired flow of things is that when looking under the Model Tree for FirstAssy.asm, and then driving down into the Relationships for SecondAssy.asm, you are unable to view or change the Design View Representation here. Under Relationships the only reps listed are Position and Level of Detail.
So I'm wondering if my scenario is a solid drafting practice and Inventor is just being a bit clunky about it, or am I bypassing Inventor's intended representation rules and FirstAssy's Design View Representation should be calling up a Level of Detail with SecondAssy instead?
