Easy I hear you say. It does that anyway. Which you’d be right about.
However, my form runs the action to add another row to the same table after saving. This opens the same form again. When you exit from this form through cancelling, which is the only way out of the loop, it doesn’t lead back to the parent table. If I add one extra row it takes me back to a grandparent of the forms related table; more than one extra row and it takes me all the way back to the landing page, which is more of a distant cousin.
Presumably this is not “normal.”
Is there a way to specify where my cancelled action/form should go to afterwards?
You may ask why I do this and not just set the form to re-open. It is because asking the form to re-open takes about considerably longer than running an action to add another row, and I need my app to be fast.
I need to enter values one after the other quickly onto different rows of a table. I’m using an action because the form auto re-open is slower than running an action on save.
I had a look to see if I could do it the way that you suggested, but the finished view doesn’t me select the form again.
Open to suggestions on a better way of doing this. I’ve had reports of issues with an auto calculated value in the form after the action has run quite a few times. It would be nice to be able to enter values into a table. I know that it is possible with quick edit, but this is too volatile as all the values can be lost by accidentally hitting cancel, and it is still experimental. Would be nice if quick edit of a table could work one row at a time.
