Hey guys, I am hoping someone has successfully duplicated a parent record along with it’s child records using the record utilities pipe on a DataTable and can let me know where i might be going wrong.
I have now been able to successfuly duplicate a record on a DataTable rule but not able to successfuly duplicate the child records.
I have set the values in the Pipe to the child table ID and the field ID of the connection field in the child table. Should these values be something different? I’ve exhausted all resources i could find without a solution.
The pipe does indeed work, we simply don’t offer support for it since its beyond the scope of standard support. It can get quite complex trying to get this working and is generally more of a implementation question vs support.
I have tested this API call and whilst I can confirm the Duplicate Parent and Child Pipe does work with a simple child table and record.
I too am also experiencing problems with using this on my real application, where the child record has a lot of fields, connections and rules running on it. In my live app only the parent record gets created. I’ll continue to troubleshoot and report the issue to support but I’m wondering if it’s timing out, has anyone else used this pipe with success?
[incidentally: the “field in the child table to use” does refer to the connection field in the format field_xxx as per @richardch372 screenshot above.
I’ve had a similar experience where only a portion of the child records are being duplicated. 47 out of 53 child records are actually being duplicated…however, in the very first parent record all of the child records are duplicated.
My suspicion is that it’s timing out (that might make sense why some of yours work and some don’t too) and we need to push equations to background queue but since I can’t change the header of the API call in this pipe I can’t experiment with that. I’ve opened a ticket and will update this post with any updates I might receive from support as it looks like at least two others are experiencing similar issues.
We are using the duplication but need to check each one as we get random results. We run another rule straight after the duplication rule which is related to the duplication and that produces randon results as well.