I see, in that case I would separate New and Update Forms altogether. Typically to add a new row you use the "+" button. To update a row you tap a row or use the Edit button.
For your use case, when you tap the "+" it goes to its normal Form and then on Form Save of THAT Form have it navigate back to itself.
However, for Editing of an existing row then intercept the Edit action to go to a custom Edit Form. If you just add the new Form, the "+" button will begin to use it instead of the default, so the trick here is to create a Slice, give it a name and set the filter criteria to "TRUE". Now you can create a view on this Slice as a different datasource and it won't interfere with the System actions.
Next, depending on how you Edit the rows, you would intercept the Row Selected actions on Table and/or Deck views (if you wish to go straight to Edit) OR create a custom Edit action to navigate to your Edit Form and show it instead of the system action, along the lines of what @TeeSee1 was suggesting (I guess he was a couple steps ahead).
LinkedIn
Twitter
