Sync Mode Immediate, create row causes iterator sync problems

Question

Hi,
I'm building an application for a client and in that I've got a master detail ADF data page.
The 'master' data is user details for the application and the 'detail' data is the various access privileges a user has related to different countries, i.e. update privilege for UK data, read access for Swedish data etc. etc.
My page consists of a summary of master details (master iterator) in read only fields, a grid of detail records (detail iterator) and for each row in the grid, a 'select' link is provided which when selected, populates an input form on the same page with the details for that row (via setCurrentRowWithKey). The user can then update the details of the row and save.
Problem I have is when a New detail record is created.
The user presses a 'New' button (bound to Create action) which sets up the input form for a new detail record. The user enters the new details and presses 'Save' (bound to Commit action). Saving causes the detail grid to refresh (row position moves to 1st row in grid), showing the newly inserted record, however the input form itself on the page still contains the details of the inserted row.
So if the record I insert should be displayed 3rd in the grid (due to an Order by I have on the VO), it does show up as 3rd. However, if I select the 1st record on the grid, the data for the 3rd is displayed in the input form, if I select the 2nd record on the grid, the data for the 2nd is displayed, if I select the 3rd record on the grid, the data for the 3rd is displayed again and so on. Selecting the 1st record again still displays data for the 3rd record in the input form.
Somewhere the iterator is getting messed up.
I always refresh the query at the prepareModel phase but this doesn't fix the issue. I'm using the initializeModelForPage method that was demonstrated in ToyStore. In fact my application is built in the style of the helper functions that were provided with ToyStore (and are an excellent help!)
Can anyone point me in the right direction to fix this problem?
I'm using JDev 10.1.2.1 with immediate sync mode.
Thanks,
Paul.

Answer 1

I thought I'd pinned this down to the fact that on the page where there is no iterator problems, the PK of the table is a sequence.
When I select any row in the grid (via setCurrentRowWithKey) on that page, the rowKeyStr for each row never changes when the page is reloaded (which is what I would expect).
On the page where there is an iterator problems, each time I selected a row on the grid via setCurrentRowWithKey, the page reloaded and the rowKeyStr for that row had now changed to something else.
The table underlying this page had a VARCHAR2 primary key. Thinking this was the cause of the problem, I added a new PK based on a sequence and set the previous PK to a unique key only. I changed all the related entity, link and view objects to reflect this. Also made sure that the previous PK field was not selected as a 'Key Attribute' under the view object dialog box. I've gone through the definition of the entity object closely to make sure it reflects the format of the table it's based on.
Still though on this one page, a select of a row via setCurrentRowWithKey results in a change of the rowKeyStr when the page reloads and also JBO-33035 errors (as I said, pages that do work based on sequence PK tables don't change the rowKeyStr when reloaded).
Any ideas on this behaviour would be welcome. Could there be something still ‘hanging around’ in the entity or view object definitions that is causing this behaviour? I'm really up against it now on this one.