Possible to associate a parameter within all types of a nested family?

[mhiserZFHXS]

Hi all,

I've been building my firms door library from scratch and my colleagues recently asked me to add a feature which would include adding a new material parameter to a nested family. However, that nested family (happens to be the door panel) has 18 types. So I now have to go through every door family I've created and associate that parameter in every one of those 18 types. Is there a way to just associate that parameter one time in the nested family and have it be associated in every type?

I don't believe this is possible, and I've searched around these forums. I've mostly figured out how to do this in bulk using the Orchid package in Dynamo, but the author of that needs to update a node for it to work properly (they've done this and will be launching an update soon).

I wanted to just double check to make sure its not possible in OOTB Revit before I post to the idea board.

[ToanDN · Accepted solution]

Do you use a Family Type parameter to select a nested type from a list in the main family?  If so, and if the Material parameter in the nested families is Instance, then don't need to associate the nested Material parameter with a parent Material parameter 18 times, but only once.

[barthbradley]

18 types as in 18 nested families?  Yes, you would need to associate each family's material parameter to the host family material parameter.  We have door families like that.  Maybe not as many panel options, but quite a few.  

[mhiserZFHXS]

Yea I switched the nested family parameter to instance and that did it. I don't know why that gave me issues. Brain fart today I guess.

[mhiserZFHXS]

No no. Its only one nested family. The geometry is super simple, literally one extrusion with voids to cut different windows out depending on the type, and then other extrusions for the glazing to match those openings. No frames or decorative panels or anything, so I figured it'd be easier that way rather than having multiple nested families.

@ToanDNwas correct and I just needed to make the parameter an instance instead of a type.