No matter how the portal is sorted, a new blank row (if the relationship allows record creation) is always at the bottom of the portal.
You could create two relationships: one with a TO that allows creation, the other one with a TO that does not.
Use the one that does with a portal that only shows one row and has a filter condition like
Put that portal above a portal into the TO that doesn't allow creation. A newly created portal row, having received its PK automatically, no longer satisfies the filter condition and will on commit 'migrate' into the lower portal, being replaced by the spare row for the next entry.
You need two TOs because the inverse filter condition doesn't work, i.e. a portal into an "allow creation" TO will always display its spare row which cannot be 'filtered away'.
Simple. Why didn't I think of that. I'll try that solution and see. I'm just trying to simplify my new FM13 template to have the least amont of anything. Less buttons, less code less everything. Minimalist that I am
Ya, thanks but I thought I made it clear that I know that. Look at the solution that erolst provided. That is a workaround. Simple too.
That is a really neat trick! Thanks erolst.