Hint wanted: EditCurrentRecord, execute, error: dead view row

Question

Hello, I'm searching for a workaround on a typical insert problem.
I have an HTML page with a <FORM> dynamically created using EditCurrentRecord.render() function. This <FORM> is used to insert a new record.
If the user, after getting an exception (for example because he didn't fill a required field) GOES BACK TO THE PAGE with the form, corrects the problem and click the submit button again, he always get the following error:
JBO-27102: Attempt to access dead view row
Imagine a <FORM> with about 50 fields, many filled up and a required field left blank...
I have extended EditCurrentRecord, so I can "manipulate" something if necessary, but please tell me further detail about this mechanism.
TIA
Fabio

Answer 1

Hi, I extended EditCurrentRecord too, I have deployed locally, and I have same problem you indicated.
If for any reason I have to return to the page with the HTML form using browser's back button, first time I post data I get the error JBO-27102: Attempt to access dead view row
This doesn't happen if the page is refreshed.
I think the reason resides in RowKeys, a runtime address generated when preparing to insert a row (look at EditCurrentRecord.render() function for details), address which is stored in a hidden field when generating the form (name "_ROWKEY") and requested later with the execute() function.
Anyway, there is a thing that I don't understand: if I comment the following lines from EditCurrentRecord.execute() function:
// if (getRowKeys().get(sRowKey) != null)
// row = (Row)getRowKeys().get(sRowKey);...even if next line of code assign a value to the row variable...
if (row == null)
row = qView.first();...why in this case, even if the row variable is not null, I ALWAYS get the JBO-27102: Attempt to access dead view row error?
I can't understand. Maybe the solution to our problem resides in that clue.