Carl Backstrom's Blog

Wow a real APEX posting can you believe it?


So I got an email from Alistair Laing asking about a certain example of mine , (AJAX) Report Pull.


He rightfully pointed out that if you used one the AJAX enabled report templates the AJAX pagination worked but the sorting wouldn't work, sometimes.

The reason for this is that the AJAX templates are a HACK! That's right I said it ,I can because I built them, sure they are a successful , well used, robust HACK but a HACK none the less.


The issue with the sorting not working is because the header links are rewritten when the page loads so that the headers no longer have normal links but have AJAX enabled links. The pagination doesn't have this issue because the AJAX code is hardcoded in and to make matters worse if you paginate first then the sorting does get rewritten to be AJAX, I told you it was a HACK.

But have no fear with just a little bit more effort you can make it sorting work as it should , Ajax Region Pull & Pagination

There are a few differences between the first example and the second example.

The main part being the javascript code on the pulling page (149)
<br /><script type="text/javascript"><br />function dhtml_GetReport(pThis){<br /> var l_Val = html_SelectValue(pThis);<br /> /*<br /> Request value of the AJAX request is being set to RP so that and a process on the page has 150 has been enabled to Reset Pagination if the Request Value is RP<br /> */<br /> var get = new htmldb_Get(null,$x('pFlowId').value,'RP',150);<br /> get.add('P150_DEPT',l_Val);<br /> /*<br /> The clip values have been changed to make sure that the only thing that is inserted into page 149 is the report code an nothing else this to make sure the proper dom elements can be queired.<br /> */<br /> gReturn = get.get(null,'<clip>','</clip>');<br /> get = null;<br /> $x('ReportDrop').innerHTML = gReturn;<br /> /*<br /> The following code gets the REGION ID of the Region you just grabbed and then initlizes the headers to be AJAX based.<br /> */<br /> init_htmlPPRReport($x('ReportDrop').getElementsByTagName('DIV')[0].id.replace('report',''));<br /> return;<br />}<br /></script><br />
On the report page (150) create a Before Header Reset Pagination Process that resets the pagination if the REQUEST is RP

On the Report Region put <clip> in the Region Header and </clip> in the Region Footer.

There are a few other ways to do this but this is the way that most closely mirrored the original example.

I have updated my Example Application Export so this is there to dig through.

Something to look forward to.

In 3.1 all of this has been fixed with the inclusion of one SUPER EXCITING new declarative report attribute.



I mean look at that! It's a thing of beauty isn't it ;) and better yet it supports all of APEX's pagination types.



EDIT: if you cut and paste the code snippet you will get all the code. I need to adjust the layout of this blog or get one of those nifty code highlighting javascript widgets.