Auto Updating Report

Question

Hello.
I am using Apex 2.2.1 and am trying to get Carl Backstrom's wonderful Auto Updating Report to work.
In the Region Template he is using REGION_STATIC_ID. What is that? How do I supply this value? In Apex 3.x there is a field in which to enter a "Report Id" when creating a report. But in 2.x, I see no such field anywhere.
I went ahead and tried to create a report using his example. I made a copy of the Standard PPR template for Theme 10 (Sand). I then copied his code into my PPR copy. When I run my report, there is no refresh and also I am getting the text "#TOP_PAGINATION#" at the top of the report.
How does one get an Auto Updating report to work in Apex 2.2.1?
Thank you for any help.
Elie

Answer 1

Hi Carl.
Thanks very much for helping me out.
I've posted my Apex 2.2.1 app onto my workspace on OTN. Of course, this workspace is a 3.0.1 workspace, and so, I see the REGION_ID field in the report region. This field is missing in my 2.2.1 workspace.
Here is the link and credential info you'll need to see my report page.
workspace = play30
username = [email protected]
password = flowers
The relavent page is page 3 - "Errlog Report".
With respect to the way you're auto updating your report, I have a couple questions.
1) The #REGION_STATIC_ID# and #REGION_ID# values -- are these the same as the region_id obtained via the query:
SELECT region_id
FROM apex_application_page_regions
WHERE application_id = :app_id
AND page_id = :app_page_id
AND region_name = 'Errlog Report';
2) You're using AJAX to auto update a report region, and so, I was expecting to see some reference to the javascript function htmldb_get(). And yet I see you are not calling this function anywhere in the javascript you're using. Perhaps the functions you are using are calling htmldb_get() behind the scenes, I don't know.
We've not upgraded to 3.0.1 because we have so many Apex (2.x) apps being used in production (and this number is increasing as more users see what we've done) that we need to find a suitable time to upgrade without affecting users too much. We read in the Apex install notes that we need to make our database instance unavailable during the upgrade (an hour or so), and so, finding this hour of space is the main hurdle blocking our upgrade to 3.0.1.
Thanks, again, for any help/advice. It is much appreciated.
Elie