Skip to main content

Replicating Interactive Report Button Layout in Classic Reports – Oracle APEX Hack

In Oracle APEX, Interactive Reports provide built-in flexibility — including the convenient ability to place buttons right next to the  search bar. However, Classic Reports don’t offer that option out of the box.

While working with a project that used the Standard template, I wanted to achieve the same clean and functional layout in a Classic Report. With a bit of creative use of jQuery and APEX region structure, I successfully replicated the Interactive Report’s button placement, giving the Classic Report a modern and consistent look.

Paste the below code on Execute on page load section

$(document).ready(function () {

    if ($('#Btn_Open').length) { 

        $('#EMP .t-Region-headerItems--title').append($('#Btn_Open')); 

        $('#EMP .t-Region-headerItems--title').append($('#P8_DEPT_CONTAINER'));

    }

});


EMP                                     -  Static IDof the classic report
Btn_Open                             -  Static ID of the Button
P8_DEPT_CONTAINER    - Static ID of popup lov 


P8_DEPT_CONTAINER is not a user-defined ID — it was copied from the browser console. This ID represents the container div that wraps both the Popup LOV field and its associated button. When we use the Popup LOV item’s static ID directly, only the input field moves, not the LOV button. Therefore, to move the entire Popup LOV (including the button), we use its automatically generated container ID instead.


Comments

Post a Comment

Popular posts from this blog

APEX - Tip: Fix Floating Label Issue

Oracle APEX's Universal Theme provides a modern and clean user experience through features like floating (above) labels for page items.  These floating labels work seamlessly when users manually enter data, automatically moving the label above the field on focus or input.  However, a common UI issue appears when page item values are set Dynamically the label and the value overlap, resulting in a broken and confusing user interface. once the user focuses the affected item even once, the label immediately corrects itself and displays properly. When an issue is reported, several values are populated based on a single user input, causing the UI to appear misaligned and confusing for the end user. Here, I'll share a few tips to fix this issue. For example, employee details are populated based on the Employee name. In this case, the first True Action is used to set the values, and in the second True Action, paste the following code setTimeout(function () {   $("#P29_EMAIL,#P29_...
Post a Comment
Read more

Oracle APEX UI Tip: Display Page Title Next to the APEX Logo

In most Oracle APEX applications, every page has a Page Title displayed at the top. While useful, this title occupies vertical space, especially in apps where screen real estate matters (dashboards, reports, dense forms). So the goal is simple: Show the page title near the APEX logo instead of consuming page content space. This keeps the UI clean, professional, and consistent across all pages. Instead of placing the page title inside the page body:         ✅ Fetch the current page title dynamically         ✅ Display it right after the APEX logo         ✅ Do it globally, so it works for every page All of this is achieved using:         ✅ Global Page (Page 0)         ✅ One Dynamic Action         ✅ PL/SQL + JavaScript Simple, effective, and reusable. 1️⃣ Create a Global Page Item On Page 0 (Global Page), create a hidden item:      P0_PAGE_TITLE This item wi...
Post a Comment
Read more

Building a Custom Debug Package for Oracle APEX Using PL/SQL

While developing Oracle APEX applications, debugging page processes and backend PL/SQL logic can be challenging—especially when values are lost between processes or execution flow is unclear.  Although DBMS_OUTPUT is useful, it doesn’t work well inside APEX runtime. To solve this, I built a custom PL/SQL debug Package that logs execution flow and variable values into a database table.  This approach helps trace exactly where the code reached, what values were passed, and whether a block executed or not - even inside page-level processes and packaged procedures Why a Custom Debug Package? Works seamlessly inside Oracle APEX page processes Persists debug information even after session ends Helps trace execution flow Captures runtime values Can be turned ON/OFF dynamically Does not interrupt business logic The Package consists of:- Debug Table                         -  Stores debug messages Sequence ...
Post a Comment
Read more