Component Priority First Level Selection?

[davis.j]

Is there a way to select component priority, but 1 level down the assembly?

I have an assembly that has a master assembly inside of it and I want to make custom views in my assembly.

I could make the views in master assembly and then reference the views in the top level assembly but I would rather keep the master assembly clean. It is also faster to just make the custom views in the top level.

I currently have to use part priority but some of my components are 3-7 levels deep so there it is a lot of manual click work to hide parts. I could use the model tree to selected components but it is easier to visualize views by directly selecting from the model space. Another way I do it is clicking into the assembly and making the view how I want it by using component priority and then returning to the assembly.

Part priority selection

First Level selection

 

[Lucas.dolinarVFXZU]

It is hard for me to understand the issue without a clear image of what the Master Assembly looks like, and how the custom views should look...
could you elaborate further? 

[-niels- · Accepted solution]

I think i understand a little....
What i normally do is:
Use part priority to select a part that i know belongs to a sub-assembly
Right-click > find in browser
Select the sub-assembly in the browser

Roundabout and probably what you are doing currently as well (or close to it)

To my knowledge there isn't a built in way to directly select the sub assembly, it might be possible through iLogic programming but you'd be spending clicks to active that as well so it wouldn't gain you much...

It might be something to put on the ideas forum...

(there are some ideas that seem to come close, but not quite what you're asking)

[davis.j]

@-niels-  Exactly. I currently use the workflow you had mentioned and other methods too.

If only there was a another priority selection for "First Level" or "one level down". 🙂

 

 

 

  

[sundars · Accepted solution]

Hi Folks,

Its a valid request and a good idea to post on the ideas forum. It should not be too hard to implement such a filter - basically when we get a selection hit on a component/part/body we would need to filter out things which are not at the first level. However, like @-niels- says, you could potentially write some automation (iLogic/vba) which inspects the selection hit and filter it out yourself. Might be easier.

-shiva

[davis.j]

Thanks for the feedback everyone, I will look into the iLogic options. 🙂