A lot depends on how/ where the script triggers are defined and what they are supposed to do. If you need to do something with the selected row, do it before delete, otherwise after. I'm assuming there is a script capturing the backspace key press. Does it not work via that script there? If on FMPA you can use the script debugger to look at what actually is going on.
The user can delete a portal row by selecting it and clicking "delete record" or click the backspace key. I would prefer this rather than a little garbage bin button because my coworkers are anarchists at heart and would most likely ignore the icon and click the backspace key.
Force them to use your icon (to which, I assume, is attached a deletion script) by opening Portal Setup and disallowing record deletion.
What trigger are you using and on what object? To capture the keystroke you have two: onObjectKeystroke and onLayoutKeystroke. Note that the will actually both fire on each keystroke. Which one is your script attached to?
The script will automatically set tags for a user. Ie. if the user adds a donation, or a portal row, the script runs and updates the tag to "active donor." For some reason, when you delete the portal row by the backspace key or an icon the script triggers (from within the portal object) never trigger. It doesn't matter what I do, if I add a new portal line it still doesn't trigger.. or if I go to the next record it still doesn't trigger.
I also noticed that when you add the very first portal row it doesn't want to commit the record until a second portal row has been made...hence the script doesn't trigger until there are two portal rows.
I also tried putting a script on the layout "on exit" but it still doesn't trigger the script.
I just realized that it does the same thing with an icon. *face palm*
Hmm..I've tried all of the triggers on the fields within the donation portal and the donation portal itself. I just realized that my other membership portal works perfectly. Which makes me think this is another relationships problem on my part.
Members portal displays records from memberships table.
The trigger updates properly.
contacts >-- memberships
Donations portal displays records from donations request table. Donations can be made by multiple donors.
The trigger doesn't update properly.
contacts --< donations request >-- donations
I'm assuming that if I create a layout from the donations request table and place a portal within this new layout that displays records from the donations table...that I may be able to solve my problem? Or... is there a way to keep the user in the contact details layout, allow them to add a new record, and have the script update without dancing around?