I am trying to add a bunch of parameters to a family. For a new generic model family, I want to reuse a number of builtin parameters from other revit categories (e.g. Apparent Load (which is a builtin parameter for lighting fixtures)). I figured out this is possible manually, by changing the family category, filling in a parameter, and then switch back to the original family category. (see video)
I want to do this because it would save me a lot of time. Because for my usecase i could reuse many builtin parameters and otherwise i would need to add all parameters and properties (like units) manually. I allready have a list of all builtin parameters using the Document.BuiltInParameters node from Clockwork (see image).
In my situation I want to create a script where i create a dropdown menu where i can select one (or multiple) of the existing builtin parameters, so that it adds the parameter to the family. Does anyone have an idea on how to create this within dynamo? all tips are welcome.
@sovitek, Yes now you extracted three of the builtinparameters, but how can i add those to the family in revit?
When i look at the parameter properties i only get null values:
Hi dont think its possible its in our family template, but you can actuelly cheat it as you do with swap category, im not sure if it good…take a look here
PS Have you tested when you shift categori its still is a builtn parameter ) [i have never tried
but you could create some familyparameter and/our shared for reuse
I clicked the link, but the conclusion there is that it is not possible…
and I dont know if it is still officially built in after the swap, but the main goal is to use the builtin intelligence of those parameters. and it looks like thats working, so i consider it a “win”.
I know it is not “best practice”, butin my uscase we are building a large family dictionary for a really specific case.
Unlikely the intelligence will work long term, as those are handled by the internal components for Revit. So while today it might hit ok with 2022, 2023, and 2024, it might not in 2025.
If you want to pursue it anyway, I would change the family category, save the family with the suffix _newCategoryName, set the parameter values, close the family, reopen the ‘newCategory’ version, change the family category, and save it again with the new type. The extra ‘save’ will give you a chance to check the intermediate stage data between file versions.