Periodically overwrite the problem

[ssean7240]

In this part, thank you for helping me solve the problem of FamilyInstance.ByPoint.

FamilyInstance.ByPoint question?

Hello, everyone In the picture, I built a multi-storey model. [image] I am going to try to place components periodically. At the beginning I grabbed the height of each floor and gave the coordinates. And use the List.GetItemAtIndex node to grab points and place the component. But I found that the output of index=0 and index=1 will only be placed in the index=0 position. Has anyone ever had this happen? [image] [image]

place-component with periodicity.dyn (28.5 KB)
place component model.rvt (3.5 MB)

I am going to try to place components periodically.
But I found that when the program is executed,
The components placed in the previous loop will be overwritten and will not remain in the model.
Is this a normal situation?
Is there a way to keep the components?

[Ewan_Opie]

A quick question, why do they need to be placed periodically? And not through some List.Lacing to longest?

[ssean7240]

This is just the test I want to do now.
I mainly want to solve the overwrite problem.

[Marcel_Rijsmus]

do you mean the element binding problem?

Is it possible to break element binding in Dynamo?

Is there an easy way to run a dynamo definition multiple times and have it write new element Id’s and not over write the old ones? I am placing CW panels by points on 2 towers and each time I write it removes the other tower panels. I get that in some cases you would want to edit the element that you just created but how do you remove the connection between dynamo and the element created? Thanks

[jacob.small]

It is an elememt binding issue. You have two options.

1. Use the timing to pull the level list/points and feed that to the element creation node.
2. Use a transaction to force each element to be created and released by Dynamo.

[ssean7240]

Sorry, I don’t quite understand the meaning of these two methods.