Hi Peter, I did provide a workaround for this. It involves creating a 2-step form:
To elaborate on this more, when the user submits the first blank form, you would set up a form rule that sets that record’s connection to the logged-in user. This way, on part 2 of the form, you can add the parent connection field, hide it from view, then add your child connection field and filter it by the parent connection field. Since the parent connection field was set in the previous form, the child connection field will only show the records connected to the parent.