So this is racking my brain. We have a template with 10 Door Family types. and when we do a site adapt we keep the template doors and then make site specific doors from the template doors. So to do this I right click the door and hit edit. then save it as a new name on my desktop then reinsert it in my file with the new name. I know what you are saying why don’t you just rename the template doors in the project to the new names. the problem is we then send to the new phase team and they also need the template doors.
So in my order and I am working on it now.
Get a list of Doors (Done)
Filter out the Template Doors (Done)
Duplicate the template doors with new site specific names (?) Duplicate Door.dyn (38.3 KB)
Hi @jarod.tulanowski , I didn’t fully understand the question—sorry about that. However, here is a way to duplicate the doors and set values by their names.
Hi @jarod.tulanowski,
Can you tell us how you would rename duplicate elements? Are you adding a prefix to those duplicate elements, or will you be changing the entire family type name? Could you show us an example of how you would rename them manually?
What does the next team do with the template doors? If you’re saving your changes as a new family then the other team can’t copy the template door types to new project door types in your same family, so what’s the need? Is each team creating their own family? Why not just have the project template contain two (or more) families from the beginning, one for standard types (template not to be changed) and one for project types (template to be changed)?
WE have client site names for areas like MU_ instead of the template name NV_ (our company name) MU being Miami university (Client name). right now I right click on the Door family name in the project browser and select edit then once open I save as to another location (Desktop)with the new name. then I load it in the project file. now I have both the template door and the new client door (even thought technically they are the same with different names)
Example Door Name Start = NV_Door Single (StudWall) Template
Example New Name Insert = MU_Door Single (StudWall)
replaced NV with MU and removed template from the name
easy answer because we tweek the doors regularly and the less doors to edit in the template the better. But your answer is not wrong Nick. just trying to make both sides happy lol
Getting closer I have all I need but now just to get it to duplicate the Element not the Element type. So just a question can you duplicate a door family? all the nodes seem to duplicate the type
OK I just figured out an issue that will put the breaks on. I think I had it worked out but the issue now is when I use the All Elements of Category node it just gets the door type names not the door instance name.
OK now I got it to just find the family and not the family type (Sweet) now how to duplicate that. man I feel I am soooo close. Duplicate Door2.dyn (48.7 KB)
Like you mentioned in your manual process, you have to save out the family with a new name in order to “duplicate” at the Family level. You can likely still automate this, but you’d have to follow the same process:
