Skip to Main Content
Feature Request FR-2447
Product Area Page Components
Status ROADMAP

20 Voters

"Requires Filter" Attribute for Report Type Components

gerard otin fidalgo Public · Apr 16 2022

Idea Summary
For reports with high-volume data, you may want to prevent the report from loading, until a filter is made, or a request is made by the user, to avoid unnecessary workload.

Use Case
IGs, IRs and other types of reports on queries that attack to high volumes of data and spends some time loading.

Preferred Solution (Optional)
As a workaround, I created a hidden item which I added to the “where” section in the query. By default, the report will load no data. Whenever the user “clicks” any part of the IG toolbar, the hidden item sets, and IG refreshes, with the data showed.

It would be a lot easier to just add a setting for activate/de-activate this feature.

This is currently on the roadmap for a future release of Oracle APEX.

Known Duplicates

Known duplicates

FR-3206
FR-3206 Only execute an Interactive Report's query after the user has created a filter from the Action menu

Comments

Comments

  • gabriel.diaz.arias OP 3.5 years ago

    This would be awesome, but not only for IG, for every report component that has serach capabilities. This is a typical workarround, to have a hidden item that is set during the first search.

  • patrick wolf Admin OP 3.5 years ago

    We should at least have a declarative Requires Filter flag on the region level. Optionally a column-level flag might be useful too which could be used to require filtering on (some) indexed column(s) to reduce the returned data and to avoid full table scans.

  • theresa.galvez OP 3.2 years ago

    Maybe add a declarative option following the same logic of Run on Initialization or Page load. So you can toggle it at design time and not mess with hidden values to trick the grid into not loading.

  • mark.lancaster OP 2.8 years ago

    The requires filter flag on a region level would be good, the column level flag would be awesome.

    I'm currently looking at performance solutions for an IG on a 600+ column table with ~130 lookups. 
    Yes - reducing the number of columns for the source query is on the list :)

  • bajanc OP 20 hours ago

    When will this feature be implemented. What does being on the roadmap mean?

  • gjaram OP 20 hours ago

    @bajanc - Simply put, they're evaluating WHEN to release it.  No timeline given but probably because they haven't implemented it yet.  The good thing is, is that it IS going to be developed, we just don't know the “WHEN”

  • vincent morneau Admin OP 17 hours ago

    The roadmap outlines the features we’re interested in and prioritizing at different levels. It doesn’t guarantee that these features will appear in the next APEX release. It is a living document subject to change as priorities evolve. This idea is still on the roadmap.