Nested generic annotation associated to fixture type

[alexanderA7AF8]

Hi, 

We have a lighting fixture family that we use nested generic annotation to tag the fixtures in RCPs, but only seem to be able to make it text field that must be manually updated.  For example, if the Family "Recessed Downright" is placed in the model and is duplicated from Type-A to create Type-B, a Lighting Fixture Tag family will update to the new type, but the nested annotation will still say Type-A.  It looks like only generic annotation can be nested, not Lighting Fixture Tags, so is there a way to set up a shared parameter so that the nested annotation updates when we duplicate a fixture?  

[hmunsell]

@alexanderA7AF8 wrote:

We have a lighting fixture family that we use nested generic annotation to tag the fixtures in RCPs, 

---

don't understand why you are nesting a Generic Annotation to tag a light fixture. we use a Detail item in our lights to show symbolically in a plan (rectangle with a angular line thru it). our lighting fixture tags read the Type Mark.

• if you edit type for the fixture
• Duplicate and rename the Type (we name the types with the Fixture type name)
• edit the Type Mark for that fixture type.
• set your Fixture tag to read the Type Mark

[barthbradley]

Is the Tag reading a Type or Instance Shared Parameter value?  

...let's clarify: what do you mean by "updating". Updating how? 

[alexanderA7AF8]

We originally used Type Mark, but we have the same issue where it would need to be manually updated when you duplicate to create a new type.  In your list below, our hope was to skip the step "edit the Type Mark for that fixture type."  so the nested annotation automatically display the duplicated Type.  

[alexanderA7AF8]

Played around with both Type and Instance, we were able to get the Instance parameters to show up in schedules the way we like, but they're still generic annotation that needs to be manually inputted.  By update, I mean it would be nice when I create a new Type, the nested annotation will display the new Type, and not a parameter text field that I need to fill in.  

[hmunsell]

have you considered using the Type Name in the tag? that way when you make a new Type (and name it appropriately) the tag will just use the fixture type name.

[barthbradley]

Yeah, I'm not following. Tags can read whatever Shared Parameters you like. You can even create Calculated Labels in a Tags.  

[alexanderA7AF8]

Is this done in the nested generic annotation family "Edit label" or in the fixture family?  I do not see it as an option when I try to define the label.  

[alexanderA7AF8]

Then I must be missing a step.  I would like the nested annotation to read the Type Name, but can't seem to find that as an option.  Thanks, 

[hmunsell]

• select the light fixture
• Edit Type
• Duplicate
• name it to the fixture type name you want displayed
• set the Lighting Fixture tag to display the Type Name

[barthbradley]

"Type Name" is a build-in System Parameter/Label available to all Tags.  

[hmunsell]

https://autode.sk/2yRgPJ9

[alexanderA7AF8]

So starting with the Multi-Category Tag has the Type Name, but I get an error message that only Generic Annotations can be nested.  With Generic Annotation, the "Select available fields from" is blank, and Type Name is not the list when you go to add a parameter.  

[barthbradley]

Generic Annotation???

Labels are what you use. 

[alexanderA7AF8]

If I understand correctly, to nest a label it needs to come from a loaded annotation family, I do not see the option to add a label directly into the family.  

[barthbradley]

Are you in a Tag Family? Do you see "Label" on the Create Tab?  

[barthbradley]

It is possible that when you said "Tag" you didn't mean "Tag".  

https://knowledge.autodesk.com/support/revit-lt/learn-explore/caas/CloudHelp/cloudhelp/2019/ENU/Revi...

...so, how do you "tag the fixtures in RCPs" ?

[alexanderA7AF8]

Yes, but I can't load a Multi-Category Tag into a family.  Looking at the thread below it seems like this can't be done:

https://forums.autodesk.com/t5/revit-architecture-forum/family-add-dynamic-label/td-p/4750727

We would like to keep our nested annotation, but want to understand the limitations.   Yes, we have fixture annotation tags when you are working in the project, but the hope was to have built in annotation in the family.  

[barthbradley]