Oracle APEX – Keep Interactive Grid Selection Across Pages

Oracle APEX provides a powerful Interactive Grid (IG) component, perfect for managing large datasets. However, by default, row selections do not persist when users paginate through the data. In this post, I’ll walk you through how I solved that and made row selections persist using a simple JavaScript tweak.

🛠️ Setting Up the Interactive Grid

To demonstrate this feature, I created an Interactive Grid based on a simple SQL query pulling data from the HZ_PARTIES table.

🔍 SQL Query Used

SELECT
  PARTY_ID,
  PARTY_NUMBER,
  PARTY_NAME,
  PARTY_TYPE
FROM
  HZ_PARTIES;

This returns a basic list of parties including their ID, number, name, and type.

✅ Persisting Selection Across Pagination

To keep selected rows even when navigating between pages, we can configure the Interactive Grid with a JavaScript function.

📍 Steps:

• Go to Page Designer.

• In the Page Rendering pane, select your Interactive Grid region.

• Under Attributes, scroll down to the Advanced section.

• Locate the Initialization JavaScript Function field.

• Paste the following code:

•         function configureOptions(options) {
            options.defaultGridViewOptions = {
              rowsPerPage: 3,
              persistSelection: true
            };
  
            return options;
          }
  

  📌 This function sets the grid to show 3 rows per page and enables persistSelection.

🔎 Additional Features

• Search works across all text columns.

• Grid supports edit and view modes (toggleable).

• Selected rows remain selected across pagination — a smoother experience for end users.

💡 Final Thoughts

This small tweak makes a big difference in the usability of APEX Interactive Grids, especially when handling large datasets that span multiple pages. Persisting selection helps users make consistent edits or actions across views.

🔗 Connect with Me

sridharutukuri@gmail.com | Linkedin | Github

Disclaimer

This content is based on my personal learning, experiments, and publicly available resources, including the Oracle APEX documentation and other community articles.
It is written for educational purposes only and reflects my own understanding and opinions.

This post is not affiliated with, endorsed by, or sponsored by Oracle, my current employer, or any organization I am associated with.