Skip to main content

Interactive Report vs Interactive Grid: Key Differences Every APEX Developer Should Know

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 behavior occurs due to a fundamental difference in how IG and IR handle filters internally.

I’ll browse and share a short summary of what I found:

  • ✅ Interactive Grid (IG) relies on an in-memory model for filtering, sorting, and dropdown value generation after the initial server query.

  • ✅ Interactive Report (IR) performs server-side queries to populate filter dropdowns, fetching distinct database values each time.

When a bind variable (your page item) is set to Memory Only, it is not persisted to session state — meaning it’s available only in the browser, not on the server.

Since IG uses its client-side model, it may lack the necessary data context to build dropdown filter values if the initial model doesn’t contain all possible distinct values.

In contrast, IR re-queries the database when building filter dropdowns, so it always retrieves up-to-date distinct values using the latest bind variable — even if that variable was Memory Only. ✅

FeatureInteractive Report (IR)Interactive Grid (IG)
PurposePrimarily for advanced data analysis, exploration, and reporting​For both reporting and data entry/manipulation, with spreadsheet-like and real-time editing features​
EditabilityRead-only; users cannot directly edit data in the report​Can be configured as editable; users can add, modify, or delete records inline​
Customizations by UserUsers can sort, filter, group, highlight, and define computations​Users can sort, filter, highlight, lock/freeze/hide/reorder columns, drag-drop rearrange columns, and more​
Aggregations & BreaksAllows aggregations, group by, charting, and breaks via Actions menu​Allows aggregations, group by, and breaks, often with more flexibility​
Multi-Row OperationsNo support for multi-row edit/operations​Supports multi-row select and operations, making bulk editing possible​
Inline EditingNot supported​Supported (if enabled by developer)​
​
Best Use CaseData analysis, exploration, exporting, ad-hoc queries, read-only presentation​Data entry, spreadsheet-style manipulation, transactional operations, data maintenance​
Actions MenuYes (provides report operations)​Yes (provides both grid and row-level operations)​
Dynamic ActionsLimited support​Extensive support for dynamic actions and custom JavaScript​​
PerformanceGood with large data; server-side filtering​Optimized for interactivity; may load more data into client side model for fast editing/filtering​​
File/Image/LOB SupportBuilt-in actions for file download/display of BLOB/image columns​; more straightforward with filesNot as straightforward; may need workarounds/plugins for BLOB/image columns​
​
Save User SettingsUsers can save their report customizations as private/public reports​Users can save modified grid layouts as private/public reports​

Note: Some information has been gathered from OpenAI. Kindly reconfirm it with official Oracle APEX documentation as well.

Comments

Post a Comment

Popular posts from this blog

Reusable JS Functions for Field Validation in Oracle APEX Forms

 These reusable JavaScript functions provide client-side validation for Oracle APEX forms, improving data accuracy before submission. They allow developers to enforce mandatory fields and ensure certain fields contain only numeric values . By using these functions, APEX forms become more user-friendly and robust , reducing the chance of invalid data entry. Step 1: Create a Static Content region on the Global Page using the Blank with Attributes template. Step 2: Paste the following code into the HTML Source section of the region. <script>     function validateInputField(inputFieldId, pageItemName, errorMessage) {         $(inputFieldId).focusout(function() {             var itemValue = apex.item(pageItemName).getValue();             apex.message.clearErrors(pageItemName);             if (!itemValue) {               ...
Post a Comment
Read more

Reusable JavaScript Function to Highlight Holidays on APEX Date Picker Item

Date pickers are an essential part of web applications, especially when users need to select dates for bookings, reports, or scheduling tasks. However, in many business scenarios, certain dates like holidays, weekends, or special events need to be visually distinguished to prevent users from selecting them by mistake. In this blog, we will create a reusable JavaScript function that highlights holiday dates in an Oracle APEX date picker. This approach allows developers to call the function anywhere in their application, ensuring consistency and reducing redundant code. By the end, you’ll have a flexible solution to visually mark holidays on any date picker item in your APEX applications. Step 1: Create a Static Content region and set it to Blank with Content under the region attributes. Step 2: Inside that region, enclose a <script> tag and paste the following JavaScript function. function applyHolidayFormatterToDateItems(itemNames) {   const holidayList = [   ...
Post a Comment
Read more

Adding Custom Buttons to Oracle APEX Date Picker Footer (Set Start and End of Month)

In Oracle APEX, the built-in Date Picker is simple and functional — but sometimes, users need quick shortcuts for commonly used dates. For example, setting the first or last day of the current month with just one click can save time and reduce input errors. In this post, we’ll enhance the Oracle APEX Date Picker by adding two custom buttons — “Set Month Start” and “Set Month End” — directly inside the date picker footer. Using a small piece of jQuery code, you can seamlessly integrate these buttons without modifying the native APEX components. By the end of this guide, your Date Picker will not only look smarter but also provide a faster and more user-friendly experience.  ⚙️ This customization is created for learning purposes. Paste the below code on execute when page loads (js) apex.jQuery(document).on('focus', '#P20_START_DATE', function() {   var intervalId = setInterval(function() {     var $footer = apex.jQuery('.a-DatePicker-footer');     if ($f...
Post a Comment
Read more