My recommendation (beyond coming to one of my AU classes next week to learn more than you ever wanted to know about bindings) is to remove all the bindings, and then use Dynamo Player or another creation method to remove the possibility of bindings being introduced. It’s possible to remove the bindings via:
UI: remove an input from the nodes which create elements, run the graph, save the graph, wire the input back in, save the graph without running it.
*manual file edits: open the file in text editor, search for
"Bindings":, and delete everything in the associated square brackets, then save the file.
bulk file edits: write a Dynamo graph to perform the same steps as the manual file edit.
node replacement: copy the node which creates elements and paste it in place (note the input wires are still attached, and a shift+click should allow you to easily reroute output wires), then save the file.
Once removed, cross session element bindings can be circumvented via:
- Multiple layers of nested custom nodes.
- Custom code in Python with ToDSType correctly.
- Zero touch nodes which intentionally avoid bindings.
- Using Dynamo Player to execute the graph
- Closing and reopening the DYN between runs without saving.
For in-session bindings you can use python nodes or zero-touch nodes which explicitly avoid any degree of binding ownership.