Skip to main content

Oracle APEX Tip: Restrict Row Selection in Interactive Grid Using JavaScript

Today, I came across a post on the APEX discussion forum where Karoly Dede raised a request to restrict row selection in an Interactive Grid. In this post, we’ll share the solution to his request.

In Oracle APEX, the Interactive Grid (IG) is a powerful component that allows users to view, edit, and interact with data dynamically. However, in certain business scenarios, developers may need to restrict how many rows a user can select at a time — for example, when performing bulk updates, approvals, or exports.

In this example, we use a Dynamic Action on the “Selection Change [Interactive Grid]” event to:

  • Detect how many rows the user has currently selected.

  • Display an error message if the count exceeds five.

  • Automatically deselect the extra rows to enforce the limit.

This approach ensures that validation happens instantly on the client side, without requiring a page submit or PL/SQL process — making the user experience smooth and responsive.

Paste the following JS code on selection change Dynamic action.

var grid = apex.region("EMP").widget();  // static ID of the IG region

var view = grid.interactiveGrid("getViews", "grid");

var model = view.model;

var selectedRecords = view.getSelectedRecords();

var count = selectedRecords.length;

if (count > 5) {

    apex.message.clearErrors();

    apex.message.showErrors([

        {

            type: "error",

            location: "page",

            message: "You cannot select more than 5 records.",

            unsafe: false

        }

    ]);

    view.setSelectedRecords(selectedRecords.slice(0, 5));

}


Demo_Application


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