This is called Element Binding and is intentional. The idea is that while developing a script in the graph editor, you will constantly be updating and modifying your graph to function in the way that you like. While doing this, it would be pretty annoying if Dynamo created a brand new instance every time you updated your file. Typically once a graph is complete and being used for production, it’s run through Dynamo Player which does not use Element Binding (it’s just a whole new instance actually). There are also ways to avoid Element Binding with Python, which you can find here on the forums. All of this is better explained in the linked post by Jacob Small.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| FamilyInstance by CoordinateSystem overwrites | 2 | 743 | November 30, 2021 | |
| FamilyInstance.ByPoint overwrites | 20 | 11016 | July 3, 2018 | |
|
Dynamo Creating Family Instance with an ID of a family that already exists in the Model
|
4 | 474 | June 6, 2022 | |
| Family Instance by Point - Replacing other families in the model | 15 | 1779 | October 31, 2023 | |
| Element ID being reused | 6 | 1203 | November 21, 2018 |