I have a Form view whose Finish View is set to “Automatic”. When I open this form from a related list inside a parent record’s Detail view, and then press Cancel, I expect to return to that parent record’s Detail view. Instead, “Automatic” sent me to an unrelated view (a different related table’s list) that had nothing to do with the record I was editing.
Setting Finish View to a fixed target (the form’s own Detail view, or a LINKTOROW expression pointing to the parent record) fixed the immediate wrong-destination problem, but a related issue remained with the built-in back button (top-left corner): after saving a record, tapping back once did not go back, it stayed on the same screen. Tapping back a second time then navigated correctly to the previous screen.
This suggests that a Save or navigation action can push an extra, unintended entry onto the app’s internal navigation history stack, so a single back press only consumes that extra entry instead of actually going back.
Expected: Finish View “Automatic” should reliably return to the actual previous view in the user’s navigation flow, and a single back button press after a save/action should return to the actual previous screen, not require pressing it twice.
Repro steps:
- Open a parent record’s Detail view, then open a related child record’s Form view via an “Add” action from a related list.
- Set the child Form’s Finish View to “Automatic”.
- Fill in the form and press Cancel (or Save), and observe that you are taken to an unrelated view instead of back to the parent record.
- Separately, after saving a record normally, press the top-left back button once and observe you remain on the same screen; press it again and observe it now navigates back correctly.