Think APEX

APEX Diff gives us a clean, intelligent way to understand how Oracle APEX evolves across versions making it effortless to pinpoint what’s new, what’s changed, and what may impact our applications. APEX Diff gives you a quick glance at what has changed between APEX releases.  By default, the application shows the latest six APEX releases on the right side of the page. we can use the filter to select any 2 to 6 versions and compare what changed between them. If we want an overview of the metadata differences between any two selected releases, we can click on either the APEX Views Diff or PL/SQL APIs Diff. Selecting the APEX Views Diff option, for example, will display the differences in columns across APEX Views between the two selected releases. For Public PL/SQL APIs, the focus is on functions and procedures. Column level differences do not apply here. The app highlights additions, removals or updated definitions in the API signatures. As developers, we can easily identify deprecat...

While browsing the Oracle APEX discussion forum, I came across a useful workaround shared by a user named blue.  His requirement was to activate a specific tab automatically when navigating from  different pages — based on the redirect source, button click, or custom navigation logic. In this blog, we will walk through how to achieve this behavior. I hope it helps you in similar APEX use cases. Step 1: Create the Tab Container Create a tab container region and assign it a Static ID Static ID: TAB_MAIN Template: Tabs Tab Style: Pill Step 2: Create Sub Tabs Inside the main tab container, create three tabs and assign Static IDs: Tab Label               Static ID Emp                EMP Dept              DEPT Location              LOCATIONS Step 3: Create a Hidden Page Item Create a hidden page item na...

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...