Hi,
I have a Revit Model with multiple groups. Within the groups some Families are placed. I want to change the Families within the groups.
Is there another possibility than ungroup, change (for example with FamilyInstance.ChangeType) and then regroup?
I further want to use the script for Revit Families and their nestes families and therefore the ungrouping could lead to some problems with losing assigned parameters to the groups.
Thank you!
Well, thereâs no easy way out.
If you have only one instance of group, itâs pretty easy to ungroup, change elements and group again.
But if you have multiple instances of group, you wonât be able to update all group instances.
But thatâs what I know, maybe Iâm missing something
Duplicate the group type, append a suffix to the group typeâs name, place an instance of the dup, ungroup the dup, modify the dup elements, regroup the elements, set the dupâs type name to the original group name, swap all instances of the original group type with the dup type, delete the original group type.
I donât recommend automating with groups for a reason, and often recommend steering away from groups as a strategy in favor of other methods to keep automation possible. Until we have a group edit API this will continue to be a pain.
⌠and hope the origin wasnât modified on the original instances.
This is a VERY good point.
SUCH an important note.
Especially since: its an issue even if the ORIGIN of the original group HASNT been changed, but a NEW origin of the NEW group type would be DIFFERENT. For instance:
FWIW, for certain types of architecture in Revit, you cant âavoid groupsâ unless you are using way crappier methods. But i fear we wont ever get real API support for Groups.
I hear you on all of the above (though I disagree with the need for them relative to other options for certain typologies I hear where you are coming from).
I know a few of the developers have said they would like to tackle it but they need the go ahead, and every time someone has to say âoh you canât do that with the API as we donât have group supportâ comes up for an internal add-in we get another internal push. As a result I am certain we will get this eventually, but no idea when that will be.
For mid sized Repetitious Arrangements (Apartments, Patient Rooms, Theaters, Bathrooms, Kitchens, Vertical Circulation banks, Storefront and Curtainwall configurations, Facade panelizations, and more, there really isnt anything else that even comes close. Trying to do all of the above with Links is an absolute joke, and it completely ruins a models ability to have truly unique items throughout the building, from a GUID perspective. Assemblies auto-duplicate themselves when things are different, which makes them a non-starter.
I keep hoping groups will get some real attention eventually, but the brutal fact of the matter is: They cant attach the phase âcloudâ or âAIâ to Model Groups, so they probably wont ever get real attention.
The fact they are a Revit feature which canât be used in design automation is actually one of the internal use cases I was referring to above.
This will get off topic fast, but they do in fact have differing GUIDS, just not differing data the way groups can. Hotels, multifamily, and kitchens I have managed with other tools without the need for groups (kitchens in particular are ideal for super families IMO), but I do hear you around the desire for groups. It is a feature which needs love and Iâll continue to advocate when and where I can.
Kitchens and bathrooms have walls in them. The moment they have walls, super families donât work. And super families donât work anyway, if youâre serious about millwork detailing. The shared nature of nested families completely destroys super families as a concept.
But we can completely agree to disagree.
I would pay money to get API development in model groups though. There is a ton of stuff we would love to do with Dynamo in model groups.
I would like to say that you already pay enough, but Iâll pass on the feedback all the same. 