Show Annotations in Nested Families in Revit 2022

Show Annotations in Nested Families in Revit 2022

timMGPWM
Participant Participant
1,243 Views
8 Replies
Message 1 of 9

Show Annotations in Nested Families in Revit 2022

timMGPWM
Participant
Participant

We have typical Electrical fixture families with nested symbols.  These fixture families are used individually as well as nested in outlet combinations.  These combination families include a number of outlets.  One such example would be services for an office workstation, including power & data outlets.  These clusters have another symbol to represent the group, and individual symbols are not wanted to be visible.  The separate outlet families are shared so that the individual outlets can all be scheduled in the project and will tally correctly irrespective of whether they were modelled separately or in combination.  This has worked perfectly in Revit 2021.  Now in Revit 2022, all the separate symbols are visible, and cannot be hidden.  Can anyone advise how I can maintain the intended function and choose if I want to view the nested symbols or not?  Revit 2022 appears to have reversed the previous functionality without the option to not view the annotations...

0 Likes
Accepted solutions (1)
1,244 Views
8 Replies
Replies (8)
Message 2 of 9

iainsavage
Mentor
Mentor

Its a new feature in 2022, probably requested by users in the Ideas forum.

https://knowledge.autodesk.com/support/revit/learn-explore/caas/CloudHelp/cloudhelp/2022/ENU/Revit-W...

0 Likes
Message 3 of 9

timMGPWM
Participant
Participant

Thanks

Yes, I was aware that it is a new feature, and have seen the below explanation from Autodesk.  Just a shame there doesn't appear to be any further detail or choice as to not automatically showing the annotation along with the rest of the family in every situation.

 

So far all I can think of as a work around is to include separate fixture types with and without the annotation, but that defeats the purpose of being able to schedule all items that from a built perspective are the same.  The only difference being how they are indicated in 2D.

 

I can appreciate that this new feature is valuable as an option, but it does seem odd for them to reverse an existing function without any choice to retain the original...

0 Likes
Message 4 of 9

RobDraw
Mentor
Mentor

The Product Feedback page is a great place for your thoughts or maybe you can be in first on the IDEAS page.


Rob

Drafting is a breeze and Revit doesn't always work the way you think it should.
0 Likes
Message 5 of 9

ToanDN
Consultant
Consultant
Accepted solution

You need to make some modifications to your setup:

 

- Open each child family and assign a Y/N instance parameter to the symbol.  Load them to your parent family.

- Add a Y/N instance or type parameter to the parent family and associate it with all children Y/N.

- Open the parent's family parameter dialog and enter 1=0 in the Y/N parameter formula box

 

Message 6 of 9

iainsavage
Mentor
Mentor

Its probably a pain to edit all your families but can you not do it with yes/no parameters in the host family mapped to yes/no parameters in the nested families? 

0 Likes
Message 7 of 9

timMGPWM
Participant
Participant

Thanks to all the above thoughts...  I do appreciate your time.  I had originally ruled out using an instance parameter as I am trying to eliminate (as far as possible) the potential for user error and having modelled content being incorrectly documented for other instances of that family in the project.  I assume that in order to map the correct visibility in the parent family, it can only be achieved if the parameters are instance parameters in the child family?...

0 Likes
Message 8 of 9

ToanDN
Consultant
Consultant

@timMGPWM wrote:

Thanks to all the above thoughts...  I do appreciate your time.  I had originally ruled out using an instance parameter as I am trying to eliminate (as far as possible) the potential for user error and having modelled content being incorrectly documented for other instances of that family in the project.  I assume that in order to map the correct visibility in the parent family, it can only be achieved if the parameters are instance parameters in the child family?...


Yes the Y/N must be an instance parameter in child families or it will turn off these families when you place them directly in the project.

0 Likes
Message 9 of 9

timMGPWM
Participant
Participant
As I expected, but I do appreciate the confirmation
0 Likes