Skip to main content

Two Interactive Reports on one Page

Within APEX you normally can't define two Interactive Reports on the same page. But sometimes you do need that kind of solution. You can use Ajax to get the data into your form, but using an IFrame seems a more elegant way. There are some drawbacks using IFrame but (as Johan Cruijff used to say) "every advantage has it's disadvantage".

But this is how it works using an IFrame:
1. Create a page (ex. 24) with an Interactive Report on DEMO_ORDER_ITEMS - set the Page Template to 'Printer Friendly' to get rid of the regular header and footer stuff.
2. Create a page (ex. 23) with an Interactive Report on DEMO_ORDERS
3. On page 23 create an HTML Region with as Region Source:

<IFRAME src="f?p=&APP_ID.:24:&SESSION."
style="width:600px;height:600px"
name="details"
scrolling="no" marginwidth="0" marginheight="0"
frameborder="0" vspace="0" hspace="0" />
4. Set the Link Column attributes of the Interactive Report on DEMO_ORDERS to:
- Link Column : Custom Target
- Link Attributes : target="details" (that's the name of the IFRAME)
- Target Page : 24
- Clear Cache : 24,RIR (will clear the IR cache on Page 24)
- Item 1 : IR_ORDER_ID as the Name, #ORDER_ID# as the Value (will set ORDER_ID as Search Item.
Now if you click on the Column Link on the left IR, the right IR gets synchronized. Isn't that cool?
See the live example on apex.oracle.com.

Comments

Stew said…
Oh that is just *too slick* for words!

Very nice!
Sujay said…
As always, good work!!!

BTW, I love the Mac style menu that you are using, I already started using them in couple of my sites.

Thanks
Sujay
Tobias Arnhold said…
Hi Roel,

would it be OK for you, if I would use your example on my ExtJS example application? Just to show how you could use several interactive reports in one page with APEX and ExtJS layout.
Unknown said…
Hi Roel,

Thanks for the suggestions.
It works great.

Regads,
Aarushi
Karriem said…
How do you deal with it putting the wrong Edit Links at the bottom of the page? It puts the edit links for the iframe target...not the actual enclosing page...
Roel said…
@Karriem: I don't deal with that. The end user won't see it (because he doesn't see those links at all). So it is just of (little) annoyance to the Developer...
Anonymous said…
Does this still work as expected in 4.0? Had it working like a champ in 3.2 but 4.0 is giving a "gReport is not defined error"
Thanks
Roel said…
The example is (still) working on apex.oracle.com - and that's version 4.0.x, so I guess your problem is elsewhere...
Anonymous said…
While the updating the 2nd report through the link DOES still work on the apex.oracle.com site, the controls on the first report DO N OT seem to. I'm looking at the one you have on apex.oracle.com...thx.

I've tested from several different machines now to make sure it isn't just my system.

Just wanted to let you know. Your posts are always quite helpful.
Kumar said…
The None of buttons on left side Orders Report doesn't work even Search functionality, is there any solution?
Roel said…
You could try it with both reports in their own iframe - in the example only the right one is in an iframe. Maybe that'll help.
Alam said…
Nice tutorial, thank you!

If anyone have problem with browser throwing "Refused to display document because display forbidden by X-Frame-Options." check here:
https://forums.oracle.com/forums/thread.jspa?threadID=2276066

Check the browser security on the shared components section.
Unknown said…
Hi Roel,

when i try this in Apex 4.1 it starts the page (23), but then it immediately redirects to page 24. So i see page 23 for a second and then it only shows page 24 in what seems it's own page, instead of part of age 23. Any ideas what i'm doing wrong?

Kind regards,
Dave
Roel said…
Sure you're using the IFRAME tags correctly? Look at the source of the page on apex.oracle.com (works again) and check that with your own source...
Anonymous said…
Hi,

But using this technique, after I made a region with an iframe, nothing from the searchebar works.

How can I solve this issue?

Popular posts from this blog

Filtering in the APEX Interactive Grid

Remember Oracle Forms? One of the nice features of Forms was the use of GLOBAL items. More or less comparable to Application Items in APEX. These GLOBALS where often used to pre-query data. For example you queried Employee 200 in Form A, then opened Form B and on opening that Form the Employee field is filled with that (GLOBAL) value of 200 and the query was executed. So without additional keys strokes or entering data, when switching to another Form a user would immediately see the data in the same context. And they loved that. In APEX you can create a similar experience using Application Items (or an Item on the Global Page) for Classic Reports (by setting a Default Value to a Search Item) and Interactive Reports (using the  APEX_IR.ADD_FILTER  procedure). But what about the Interactive Grid? There is no APEX_IG package ... so the first thing we have to figure out is how can we set a filter programmatically? Start with creating an Interactive Grid based upon the good old Employ

apex_application.g_f0x array processing in Oracle 12

If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one: then you disable the " Escape special characters " property and the result is an updatable multirecord form. That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for

Stop using validations for checking constraints !

 If you run your APEX application - like a Form based on the EMP table - and test if you can change the value of Department to something else then the standard values of 10, 20, 30 or 40, you'll get a nice error message like this: But it isn't really nice, is it? So what do a lot of developers do? They create a validation (just) in order to show a nicer, better worded, error message like "This is not a valid department".  And what you then just did is writing code twice : Once in the database as a (foreign key) check constraint and once as a sql statement in your validation. And we all know : writing code twice is usually not a good idea - and executing the same query twice is not enhancing your performance! So how can we transform that ugly error message into something nice? By combining two APEX features: the Error Handling Function and the Text Messages! Start with copying the example of an Error Handling Function from the APEX documentation. Create this function