I’ve have placed several families in the project environment and I’m able to update the families or their locations without any problems as longs as long as I stay in the same session. If I close the script or it loses “connection” which sometimes happens when you open a new family, family template or project file and return to the project where dynamo was pointed too in the first place, Dynamo will place new families over the already existing families when I run the same script. This means that i’m unable to update anything in the project environment without first having to delete all placed families before I run the script. How can I prevent Dynamo from placing new families over the already existing families?

That’s really dependent on how you’re placing them currently.

In this recent project, I have adaptive component panels placed on a points generated in Dynamo. I have walls created based on curves in Dynamo. I have roofs also created trough curves either selected in Revit or created in Dynamo. And I have several line based families. The first time I placed the families, everything went as expected. As soon as I closed that Dynamo session and reopen it and rerun the script, it places new family instances. If i’m not mistaken, new roof instances are not placed if there is an existing floor which was placed previously by Dynamo in a different session.

This is expected behavior. Dynamo runs every node from scratch each time you open the file. Using some list management to drop the entire dataset early in the graph before closing, then undoing in Revit should keep the Revit work, and make it so you don’t re-create the stuff you just made the next time you open the file.

I would actually say this is not expected behavior, element rebinding should work when opening a dynamo file you have saved (thats why we save giant amounts of element binding data into the dyn file) so if it’s not working please report a bug.

So basically Dynamo should not recreate elements when the file is opened and rerun. If it does, it’s probably a bug, right?

yes, though there are types that Dynamo cannot reassociate because the revit API has no facility to update them, I think import instances are one of those cases. I know there are also some issues with nested custom nodes.

I had a similar issue with adaptive components in an AC family sometime ago. Every time I ran the script, new adaptive components where added. [image] How to update adaptive components without dynamo placing a new set of components Revit I’ve create a script to place adaptive components on points. I’ve selected the edges of a generic model to use as a framework for the point. When I change the height of the generic model the framework adjusts as expected, however it places new adaptive components families on the updated framework alongside the previously placed AC’s. Every time I run the script or set dynamo on automatic and change the height parameter, a set of new components are placed. Is there node or a workflow to simply ad…

How can I prevent Dynamo from placing new families at each run?

Revit

Thomas_Vogt February 2, 2018, 3:04pm 6

also discussed here: Running Dynamo and keeping objects created

Topic		Replies	Views
Place new family instance each run Revit	25	12305	December 9, 2016
Adaptive families are placed again while reopen dynamo Uncategorized dynamo	5	675	November 14, 2017
Element ID being reused Revit	6	1229	November 21, 2018
Using Dynamo to place multiple instances in a Revit Project Revit	16	8738	August 29, 2022
How to create Permanent element by dynamo Revit	4	1097	November 16, 2021

How can I prevent Dynamo from placing new families at each run?

Related topics