Hi All,
I believe that this may be a bug or perhaps I’m missing something obvious.
I have a function that is creating 175 objects in the first step and then creating object relations in the second step. I know that you can only do 100 objects at time and have broken up the objects into two separate lists below the threshold which should over come that constraint.
The issue I’m seeing is relations are inconsistently being created. At times all 175 are set up just fine, but usually only the “second half” of the objects have relations established.
I’ve validated that all 175 Objects are being created and that my sublists contain the objects I’m looking for.
Here’s my logic
Hello @Aaron_Alpeter,
Thank you for reporting this issue, I was able to reproduce it.
I have created an internal ticket for our backend team, you will be notified about the updates here in this thread.
Regards,
Stanislaw
Hello @Aaron_Alpeter,
you’re using the block set relations, which overrides the existing relations. So this behavior is expected.
There is a difference in how Add Object Relations and Set Object Relations work.
Setting a relation - If the parent had other child objects prior to the operation, the relation between them and the parent is removed. This is a replacement operation.
Adding a relation - adds specified child objects to the collection of existing child objects. This is a concatenation operation. For one-to-one relations, if the parent object has a child for the specified column at the time when the operation is called, an error is returned back to the client.
So if you want to add more relations in the column, you need to use the Add Object Relations block.
Regards,
Stanislaw
