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!

Cascading LOV default behavior?

davef06Oct 4 2018 — edited Oct 6 2018

Hello,

I have a v5.1 modal CRUD form that includes a parent and child cascading LOV:

- the parent is based on a query that is filtered using the value of two application items. This list populates properly on page load in every scenario, though it often returns just a single row.

- the child is based on the value of the parent (obviously), as well as an application item.

Below are additional details.

The form includes many controls including the following select lists:

pastedImage_0.png

The Fund select list is based on an LOV that filters based on 2 different application level items:

pastedImage_11.png

In the case above, the Fund select list correctly has a single value, which is displayed.

The PSP select list is based on an SQL statement:

pastedImage_9.png

In the situation from which the above image is taken, the SQL statement should be returning 37 rows.

The child LOV populates and displays properly when the form is displayed in 'update' mode. However, in 'create' mode, the child list does not populate until the parent is changed. (This is problematic, particularly when the parent returns just a single row.) I have reviewed the debug logs and the browser inspector, and it appears that everything is running as it should; there are no errors. I've tried changing the "optimize refresh" option to no effect. I also tried adding a Page Load DA to refresh the LOVs but that removed the existing database column value in 'update' mode.

My questions are:

- at what point in the page load for a create does the parent LOV get populated?

- I'm thinking I'm missing something simple. What is it??

Thanks for any assist.

Comments
Post Details
Added on Oct 4 2018
3 comments
3,307 views