I encountered such issue several times. And it happened when I copy a page or region with items. Instead of spending time searching for solution, I decided to delete each item and recreate new items.
I've deleted the form region and related processes/branches etc and re-created, getting the same results.
Next step is to generate a new page, copy my report definition and try again.
Can you try that on OTN and to see if you can reproduce the same error.
I've tried without success - I think it may require a specific sequence of events.
I'll see how I go recreating the page, but I thought there may be a way to tell APEX to sort itself out.
Well I simplified this right down to running through the create "Form on a Table with Report" wizard, using all the defaults I could and it still behaves this way in my environment, but not on apex.oracle.com
I tried this with two separate tables; always using PK (not rowid), with & without specifying sequence; classic and interactive.
I always had to set the pk value protected = no to avoid the manual alteration error, then it still offset the values.
Something is really off, and my mouse has been lucky to survive the ordeal!
This is something I've done dozens of times before. I just tried it in another application with success, surely there has to be a way to clean up whatever is going on behind the scenes?!
Further to this, existing forms in this application are now exhibiting the same behaviour.
I've exported and re-imported the application, no success.
1 person found this helpful
Well this is a day of debugging I'd rather have back.
With a form of Rubber ducking my colleague helped me notice that the number of items being displaced was equal to the number of page zero item I added recently.
These items were placed in my menu region, which happens to be region position 7.
I had commented out a section of my page template
<!--<header id="uHeader"> <div class="apex_grid_container clearfix"> <div class="apex_cols apex_span_12"> #REGION_POSITION_07# <div class="logoBar"> <h1><a href="#HOME_LINK#" id="uLogo">#LOGO#</a></h1> <div class="userBlock"> <img src="#IMAGE_PREFIX#f_spacer.gif" class="navIcon user" alt=""> <span>&APP_USER.</span> #NAVIGATION_BAR# </div> </div> </div> </div> </header>-->
but this content was obviously still being generated.
At some point during the page submission, this disturbed what apex was doing - somewhere these 'duplicated' yet commented field definitions were causing apex_application.accept to store the values in locations offset by the four P0 items.
I often look to page zero for potential causes to strange issues - but this one initially beat me.
This sounds similar to the problem we were having;
Partrick has replied to that post, you have to put the P0 items into region anywhere outside the header.
Thanks for the reference, though I wouldn't be surprised if that's jQM specific.
My behaviour is restored - my items are below the <form>, and now not duplicated within HTML comments