Skip to Main Content

APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

APEX 24.2 Regression on IG: "No data found" while changing or resetting reports

Nikola VelinovSep 23 2025

First of all, I would like to take this opportunity to once again congratulate the APEX team on this wonderful piece of software. Although APEX doesn't cost anything extra, it is of great value to us customers and to Oracle as a whole.

Now to the specific issue. We plan to upgrade our production systems to APEX 24.2, most likely 24.2.7. During testing, we noticed that in Interactive Grids, when switching reports (Primary, Alternative, etc., regardless of the switching direction) and when resetting IG reports:

The message "No data found" appears while the data is being loaded, even if data is found and displayed after the loading process is complete. This is especially noticeable when the query execution takes several seconds (sophisticated query on large data sets).

This behavior occurs at least with APEX 24.2 Patch 7 (tested on premise) and Patch 8 (tested on oracleapex.com).

Here's a simple example page with an IG to illustrate this. When you switch or reset reports, "No data found" is displayed during loading: https://oracleapex.com/ords/r/nvtest1/app1/testpage-1

You can also see it in these screenshots:

Expected behavior: "No data found" shouldn't be displayed during loading.
Not in APEX apps, and sure not in any other app in the world, whether APEX or other technology. Because "No data found" can obviously only be determined after the loading process has finished, not during it. It must be some kind of regression, because in earlier versions of APEX, "No data found" wasn't displayed during loading processes.

Now, two questions for the APEX team:
1. Should we create a ticket through "Oracle Support" (we are paying customers) for such a fundamentally obvious issue that affects every APEX user who uses IGs? Or could you please create a ticket internally?

2. Until this is fixed in a future patch or release: Is there a simple and reliable workaround? Perhaps a few lines of JavaScript placed centrally (e.g. on global page 0 or something similar) that fix all IGs in an app? I'm not sure who the right person to contact is, so I'll try @john-snyders-oracle , @jayson-hanes-apex-pm-oracle and @steve-muench-oracle - please help! :)

Kind regards
Nikola

Comments
Post Details
Added on Sep 23 2025
2 comments
447 views