Is there a bug on ParameterFilterElement.ByRules? Each time I change the Name the node overwrites the old filter with the new one. Perhaps it should be changing the element IDs?
A further attempt…Multiplie ParameterFilterElement.ByRules Failed Attempt.dyn (44.6 KB)
That’s expected behavior as that node uses the so called Element Binding and remains attached to the originally created element. This is useful when you want to change the name or parameters of a created element in the Automatic execution mode. It’s not so useful when you want to create multiple elements or filters like in this case. It’s just the way it is, and i don’t see this changing in the near future.
Ps. Workarounds for terminating that connection exist. Things like “saving the workspace as”, or deleting the node that created the original element. They are not ideal, and when i don’t want this behavior i usually script up a Python node as they don’t have element binding.