Error-Message "Item not defined on current page" after Page submit - AJAX

Question

Hello,
a lot of subpages (regions) are loaded over htmldb_get and displayed on a master page.
The parts loaded over AJAX are reports. The report regions of these reports contain a hidden and protected field, which hold the page number (&APP_PAGE_ID.)
This was necessary because I had to overwrite the standard pagination function $a_report on the master page. Otherwise the standard pagination function uses always the page number of the master page and not the page number of the loaded subpages. The overwritten function $a_report is placed in the master page header and searchs for the hidden + proteced field, containing the page number of the loaded subpage.
This works already fine.
But after submitting the master page with before loaded subpages over htmldb_get, I get following error message:
Error Item ID (15348310159873659) is not an item defined on the current page .
Setting the hidden + protected field on the subpage to never display, the error message disappear, but the pagination function doesn´t work any more.
Where is the mistake I made?
Greetings
Michael

Answer 1

Hello Ben,
yesterday evening I read in short your answer, but today I can´t see your answer. Have you edited it again?
My pagination function works fine and I would maintain it if possible.
But now a new feature is requiered, which require a submit on the master page. The submit on the master page is not possible due to the hidden field on the loaded subpage, containing the page number for the pagination function.
Using a normal text field (not saving state) works as long as the text field is visible (condiational view != never). But this information shouldn´t be visible to the user.
I thought, perhaps a cleanworkaround exists.
As dirty workaround I could place the information about the actual page number in the report themself (static invisible column). But as soon as the column is invisible (not shown), I have no access on this value
With a normal hidden html-input-element (not a APEX-Item) in the report regions header of the subpage, holding the page number, I get a http 400 error on page submit.
An I-Frame is not really a solution, because the master page contains several subpages, which should only be loaded and displayed on demand and not immediatly on page load.
Greetings
Michael
Edited by: user6044915 on 31.03.2009 00:27