Skip to Main Content
Feature Request FR-4026
Product Area User Interface
Status CLOSED

5 Voters

Have Content Row visibly select Current Selection Page Item

jmattgiroux Public · Sep 25 2024

Idea Summary
The Content Row region has a Row Selection section in Attributes.

Currently, if the Current Selection Page Item changes, the Content Row region doesn't visibly update to reflect that.

The idea is that on changes to the Current Selection Page Item, the Content Row region visibly updates (similar to how a Checkbox page item shows which values have been selected).

Use Case
This would help complete the Content Row region's features. It already has a Row Selection section that lets developers use the Content Row region with a Form, so this idea would just improve the feature to the level of more common page items. 

The Content Row region would be useful for displaying options that have extra data (for example, we could display the name of an option, how much the option costs, the estimated time frame for the option, and other details, all simply selected from a table, instead of having to prepare all the data for a Checkbox page item where we'd have to spend a ton of time formatting everything).

My team's current plan is to create custom plugins to serve this purpose, since we need the formatting of the Content Row, but due to this issue, we can't use the Content Row region.

Preferred Solution (Optional)
The preferred solution would be to have the Content Row's Current Selection Page Item update the Content Row visibly, so that when we load in a page (and set the value of the Content Row's Current Selection Page Item), the correct rows are selected already (similar to how a Checkbox page item would behave). 

This could be accomplished by dispatching events to select the rows that correspond to the values stored in Current Selection Page Item, or by updating the CSS classes and element attributes of the rows to indicate which options are selected.

We reviewed this idea carefully, and while it was interesting, we concluded that due to all the internal implications we need to take into account, it is unlikely to make its way into APEX.

Comments

Comments

  • john.snyders APEX Team OP 1.5 years ago

    It is intentional that the Current Selection Page Item attribute is one directional from report selection to item. 

    Initializing the selection in a report that supports pagination is more complicated because the selected record(s) may not be initially rendered on the client. 

    While we want to support some way of setting initial selected records in the future, it will probably not use the current selection item. 

    Currently the only way to handle setting the initial selection is to use the documented API setSelectedValues

    https://docs.oracle.com/en/database/oracle/apex/24.1/aexjs/templateReportRegion.html#setSelectedValues 

    This will also only work if the client currently has the record(s) to be selected loaded.

    Currently there is an API to set an initial selection so the requested functionality is already possible but in a different way and we may in the future make it more declarative but in a different way from what is suggested. So this idea will be closed.