Think APEX

In this blog, I demonstrate how to leverage the built-in navigation feature of Oracle APEX Interactive Reports (IR). Normally, IR allows you to redirect to other pages by passing column values to target page items with secure, automatically generated checksum values. However, my implementation goes a step further: based on specific column values, I dynamically choose the target page and navigate accordingly. For this example, I use the default EMP table. The interactive report displays employees grouped by department number, and depending on the department number (column value), the navigation redirects to different pages. Additionally, the relevant values are set in target page items for further processing. This approach showcases dynamic, multi-page navigation driven by column values in an IR, enhancing user experience by routing them contextually based on the data they interact with. Create an Interactive Report using the EMP table. In the Attributes section, under the Link settings...

Hi Everyone! 👋 Recently, I came across an interesting behavior in Oracle APEX that’s worth sharing. I had a page containing two reports — an Interactive Grid (IG) and an Interactive Report (IR) — both based on the same SQL query. The query included a bind page item in the WHERE clause to filter data dynamically. As per the requirement, I set the page item’s Storage Type to Memory Only . When the user clicks the Submit button (handled through a Dynamic Action), both the IG and IR regions refresh perfectly, and the data displays as expected. However, I noticed something unusual: when clicking on a column heading in the Interactive Grid to use the built-in column filter dropdown , it displayed no values . On the other hand, the Interactive Report showed the distinct filter values correctly for the same column. Note: To make the Interactive Grid column heading dropdown filter display values, the page item’s storage type must be set to Session State , not Memory Only . ✅ This behav...