With the new Current Table Portal (aka master-detail), you can click on any portal row, and that record is selected in the base context for that layout. FINDS and SORTS within the base context, directly impact the portal content, which is awesome.
However, I have not figured out how to IGNORE a blank portal row. IF a user was to click on a blank portal row, and a OnRecordEnter script trigger was to say, go to a layout / card / tab / slide control, to reflect detail, the blank record selection goes to the last active record, ignoring the location of the blank record click.
Needless to say, this could create some data quality issues with users.
Yes, you can always revert to traditional portals and script the interaction. You can also place a transparent button over the row and capture say, the primary key and code the interaction.
Those approaches defeat some of the key benefits of using the new current table portal.
Anyone know how to get around this limitation, while maintaining the new portal type?