Changing Multiple Family types within a family in a project using Dynamo
Changing a Family Instance from one Type to another Type should be pretty straightforward - SetParameterByName works here:
The issues I usually see in this workflow:
- Trying to cross-pollinate - you actually want to swap family files, not family types. Usually you wind up placing down a brand new family instance to avoid dealing with differences in reference planes, hosting types, etc.
- List management - you mentioned 10 families, 2 types, and an unspecified number of instances actually modelled in the project. This is going to require some amount of mapping / list level management / lacing checks. Once you post your progress we can comment on most direct option.
- Geometry conflicts - if the family type parameters modify geometry in such a way that hosting fails, you might wind up with error generation on the Revit side.
I am new to this, so I apologise in advance.
I used your example of selecting individual items and managed to get it to work with switching a Full version to and Empty version. That gives me hope that it can be done, so thankyou very much for assisting with that. 🙂
I have included the attached image showing my next stage of figuring this out, by only using one family first. Main Module 1.
The piece below it just shows the other module names with their respective numbers and that they have a full and empty version.
Obviously, what I have done doesn't work, but it is the closest I have got to a simplified version to try and put across what I am after.
I had managed a very long winded approach previously, which did change the list of Full modules, to show Empty versions, but couldn't see how to apply it to the model itself.
I sense down the line I should be able to collate families in the project, perhaps by asking for any name that contains full. Then ask to switch them out with their full version.
Really appreciate any assistance or advice you can give on this.
Thankyou
Of course I need to go through all that to THEN see where I had gone wrong!
Sometimes just talking about it does it!
Only question now.......it is possible to include all the versions like this or shall I just copy and select the alternative modules for each one?!
Okay, so you noticed that the value input needs to be the Type element and not a string, great!
Do each of the Types in each of the families follow the same naming convention? If you do, you can do a workflow like this:
If the naming conventions vary, you'll have to try something like a Contains filter on the names to do a partial string match.
Alternatively, you could try list management by pulling all the types for all the families:
The normal list is sorted by elementID (oldest type is index 0), but you could also do an alphabetical sort. Basically, whatever gives you a consistent result against all Types you work with.
Given that the intent is to simplify the work for others, the easiest quality control option would likely be maintaining a consistent naming convention versus using sorts/ordered lists.
