Tag Family Instance Parameters

[casquatch]

It would be nice to have some instance parameter options for tag families.

For instance, I have a duct tag with many different options. Rather than having a ton of types to cover all possible scenarios, it would be nice to have the ability to have visibility check-boxes as an instance parameter. This way I could build some Types to cover the main tagging options, then have some instance properties for things that aren't as "type" specific.

Currently I might have Types for:

    Duct Size - Transparent

    Duct Size - Opaque

    Duct Size - Existing - Transparent

    Duct Size - Existing - Opaque

    Duct Size - Transparent w/ Elevation TOD

    Duct Size - Opaque w/ Elevation TOD

    Duct Size - Existing - Transparent w/ Elevation TOD

    Duct Size - Existing - Opaque w/ Elevation TOD

    Duct Size - Transparent w/ Elevation BOD

    Duct Size - Opaque w/ Elevation BOD

    Duct Size - Existing - Transparent w/ Elevation BOD

    Duct Size - Existing - Opaque w/ Elevation BOD

If I have the option for some of these options as Instance parameters I could have Types for:

    Duct Size

    Duct Size - Existing

With these parameters as Instance properties to be controlled on an as needed basis:

   Transparent Tag / Opaque Tag

   Elevation BOD

   Elevation TOD

Maybe I'm thinking about this in a different way that others normally do, but I'd like to have a single tag with the different options built in, rather than a ton of tags to load in/have in the template, etc.

[Anonymous]

Allowing to tag by instance and not just by type.

Adjusting the width of text in main file and not only in family.

[Anonymous]

Adjusting the width of the label of tag family in main model is great idea!

[lionel.kai]

We accomplish something similar (with framing) with a tag family with various types, but invariably there's an option that we didn't think of (or that's specific to a particular project) that we have to create a custom family for... 😞

[casquatch]

Same Idea here:

https://forums.autodesk.com/t5/revit-ideas/tag-family-instance-parameters/idi-p/7057237

[casquatch]

I have a similar idea for another instance based parameter within tag families. It would be great if both of these were implemented

https://forums.autodesk.com/t5/revit-ideas/allow-tag-s-quot-rotate-with-component-quot-as-an-instanc...

[Magnus.B]

This is much wanted, currently having like 20 types on my pipe tags, just to cover some basic combinations. An instance parameter would solve much. For example I have an over or underline that varies depending on size (number of digits)

[jkarben]

Yes. Do need instance parameters for pipe tags too. Would like to control arrow visibility and position.

[PieterL_TM]

Give us Instance Parameters for tags, please. This would be handy for example for controling the visibility or size of a frame or border.

This is an issue that has been raised multiple times on the official forum. 

I hereby also kindly request that you listen to the feedback of your users and use this to keep improving Revit. There's multiple issues from even over 10 years ago that still haven't been solved...

[sduarte_QD]

Yes, please implement this.

I understand the reason why the software was design not to (see this link from 2015 https://revitoped.blogspot.com/2015/02/tags-and-instance-parameters.html , BUT it is very usefull in the following example situations:

- Room tags with instance graphic option (say the spacing of the text for smaller rooms)

- Pipe arrows (so that we can use select all in view with the revit default tool)

I bet that there ara many more...

[cprice]

Labels within a Tag should have a "Width" instance parameter that I can then associate to a parameter if need be.  For this to function properly you would also have to open the ability for Tags to have instance parameters.

Whilst there are several posts that mention this, I wanted to focus this request on the Width to control the wrapping.  I understand the complexity of trying to make a Tag have similar functionality as Text, particularly when a Tag can obviously include geometry and various other parameters that text can't.  The above solution would allow you to individually drive each label (as there could be multiple within a single tag family) via a Width parameter (which may even have a formula associated with it).  Other suggestions of making the controls visible in the project would be confusing and wouldn't solve the fact that there could be many labels in the one tag.

Current workarounds of having multiple labels of varying widths and controlling them with visibility or different families is painful and never allows you to achieve each individual Width requirement.  There are plenty of cases where 5+ different widths may be required in a project.  Then you have all the different parameters you may want to display, it just becomes ridiculous.  By having a Width parameter on a Label that can be linked to a parameter would eliminate this problem.  If I have some sort of box around the tag as a masking region, (as the border option on text is inadequate), I could drive the size of this via formula to match the text changes.

As mentioned in other posts it would also be very useful to link the "Justification" of each label to a type or instance parameter.

There are numerous other features that are missing from tags but they are covered in other ideas so I'll keep this focused.