Project parameters in door Family (nominal Height)

[nathaniel.mcmahon]

Want to use the revit standard concept_door type type in a project that has existing default revit doors that use the NominalHeight project parameters which the door tags use to display height. Thing is the concept_door family doesn't have the NominalHeight project parameter and I'm not sure how I add it to the new family so the new door display their height in the tags like the other ones. Any ideas, I know how to add shared parameters but I don't really want this.

[Samantha-G]

Is this a tag you created?

[nathaniel.mcmahon]

standard door tag, tag label uses project parameter NominalHeight

[Samantha-G]

I do not have this Door, can you post the door and tag family?

[nathaniel.mcmahon]

Thanks here's the guys involved

[Samantha-G]

Nominal Height is what the parameter is called in the family, but it is just referencing the Height Parameter in the door. Does that make sense? That is why you cannot find it.

[nathaniel.mcmahon]

Yes but as far as I understand that NominalHeight parameter in the family is a project parameter which is why it can be picked up by the tag label. How do I add a project parameter to the other new door family? I could do it with shared parameters but that's a nuisance in this case. 

[Samantha-G]

Are you wanting to schedule these is that why you are being specific with the parameter name?  I am asking because both of these doors, are just referencing the Height and Width parameters, so you could have the tag do the same. Shared parameters are usually the go to, when creating door parameters, so you may not want to deal with them, they may be your best option.

[nathaniel.mcmahon · Accepted solution]

I have a project full of doors and tags already set. 

The tag takes the NominalHeight parameter.

I can't seem to give the new door the appropriate parameter named NominalHeight which works with the existing tag. 

[Samantha-G · Accepted solution]

Unfortunately I am not able to get it to work either.  I was a BIM manager for a long time, if this were happening to me, I would probably recreate the family and see if that corrects it, the family could be corrupt.

Before recreating the whole thing though, I would make it very basic and see if it works.

[nathaniel.mcmahon]

Right sorry. I've exported the existing NominalHeight to the shared file and then created a new parameter in the new door with a shared parameter to the same. It now works.

I'm confused because before I exported the original NominalHeight parameter it didn't appear in the shared parameter file but was indictacted in the parameter edit box as being a shared parameter. I presume this meant it was an ootb/ project parameter. So I was and am still wondering how to add or make visable in the type properties of a family an ootb or project parameter without having to go through the export an existing then shared route. Make sense? thanks for you input. 

[Samantha-G]

Nominal Height is not OOTB, and project parameters would not work for a family.

[nathaniel.mcmahon]

so ootb parameters should always be visible in the type dialogue box? You don't have to call them up to use them?

[Samantha-G]

Yes they should be available, for you to choose.

[barthbradley]

Sounds to me like you aren't the author of the Families -- or the Shared Parameters "NominalHeight" and "NominalWidth" -- which are NOT Revit in-built Parameters. So you don't have the source Shared Parameter Text File.  This is not at all uncommon. 

Solution: Export the  "NominalHeight" and "NominalWidth" that are in the "Flush_Frame_Door" Family (the one that's working) to your own Shared Parameter Text File, and then re-associate the "NominalHeight" and "NominalWidth" parameters that are in the "Flush_Frame_Door" Family.  You do this by opening the "Flush_Frame_Door" Family, click on one of the two Parameters, click Edit Parameter,  press "Select" under "Shared Parameters" and then browse to the newly exported parameter of the same name (probably under "Exported Parameters").  

[barthbradley]

Important to know, is that Shared Parameters are shared by virtue of their GUID -- not their name.  In other words, you could have two identically named Shared Parameters that are not shared.  Something to keep in mind when using content from other sources.