Tabular form - Insert vs update
Apex 4.2/Oracle 11gR1
I have some tabular forms which ADD and UPDATE rows but instead of using the Add button and presenting an empty row, it basically makes-up rows that don't exist in the underlying table by using an outer-join in the query. Basically the idea is to default as much information on the row as possible and when the user fills in the editable columns, the built-in MRU process (as I understand it), finds the PK column blank and proceeds to INSERT the row instead of UPDATE it. The table has a row-level trigger that fills in the PK from a sequence.
All this works swimmingly well on Apex 4.0.2. But after the upgrade to 4.2, the MRU throws the usual scary error about Current version of data in database has changed since user initiated update process. current row version identifier = "xxx" application row version identifier = "yyy"
Any idea how to make this tabular form trick work in 4.2 without major surgery to the page?
Thanks