Tagging door function

[hwo_osa]

Our company is trying to update our door tags to differentiate between interior / exterior doors.

We manage this information via the built-in door type parameter "function".

Alas, tagging this vital part of information is not possible: The Revit gods have decided that "function" shall not be taggable, unlike other built-in door parameters like "Finish" or "Comments" or "Frame type".

Which begs the question, what to do? I really don't want to add another redundant parameter just for tagging purposes. Or am I missing something?

[azad.Nanva]

What is problem with using your parameters?

[hwo_osa]

@azad.Nanva not sure what you mean? When I edit the door tag, the "Function" parameter ("Funktion" in german) is not available to use in tags:

[azad.Nanva]

---

@hwo_osa wrote:

I really don't want to add another redundant parameter just for tagging purposes.

---

Yes,it is correct but you can define your own Parameter and use it in Tag

[hwo_osa]

@azad.Nanva yes, that much is clear. My problem is that creating an additional parameter for this purpose would make the process of creating / managing door types more error prone than it already is, because it is one more piece of (redundant) information that our architects have to look out for when creating / editing family types.

[azad.Nanva]

You can write this in Ideas

[hwo_osa]

This idea has been added to the ideas forum: Make the built-in door function parameter taggable - Autodesk Community

[blank...]

---

@hwo_osa wrote:

@azad.Nanva yes, that much is clear. My problem is that creating an additional parameter for this purpose would make the process of creating / managing door types more error prone than it already is, because it is one more piece of (redundant) information that our architects have to look out for when creating / editing family types.

---

Sorry, not getting it. How would it be different for them to enter door function in either "Funktion" or "Funktion_Custom" parameter? They have to do it either way, you just add the parameter to the family, they don't even have to know (or care) if it's built in or a custom parameter.

[hwo_osa]

@blank... No, I don't think this is a good idea. The solution you propose will either lead to inconsistent parameter values between "Funktion" and "Funktion_Custom" because people will ignore the built-in parameter, leading to confusion for new team members, project managers or generally everyone that isn't aware of the process, or it will require people to dutifully fill in two parameters ("Funktion" and "Funktion_Custom"), which I guarantee will not happen.