This content has been marked as final. Show 6 replies
have you checked this video [url https://blogs.oracle.com/shay/entry/dependent_lovs_in_an_afquery_c]Dependent LOVs in an af:query component
Yes - I did review that video, and as I mentioned above, I have set "auto submit" to true on the attributes in the search view that are cascading LOVs
Hi. AutoSubmit is definitely a must, but I think you have to set the appropriate partialTrigger as well - if you haven't done so far.
Since the dependent LOV drop downs are generated dynamically (as part of a af:query) - I'm not sure how or where I would configure the partialTrigger in this situation.
I understand the concept of partialTriggers in general - but with the dynamic nature of af:query - I'm not sure where I would configure it in this instance.
- Under "Dependencies", added the attributes that the LOV is dependent on
thi sonly refreshes the attribute when one of the other attribute values changes. From your description I am missing the point in which you explain that you defined a View Criteria on the dependent view to filter the result set based on the first attribute. You then would have explained that you set the View Criteria when creating the second LOV and have it referencing the parent attribute for the bind variable. So I am not convinced the implementation is correct.
Hi Frank -
It is possible the implementation is not correct - especially since it isn't working :-).
In the second LOV - I have a view criteria configured to filter the LOV based on bind variables. The bind variables are referencing the parent attribute through the views "View Accessors" section. In editing the view accessor for the LOV - the view attributes are mapped to the binding variables.
On my search view, I have two LOVs on two different attributes.
My assumption (possibly incorrect) is that when the first LOV is selected, the view attribute changes. The "auto submit" on the first attribute "UI Hints" combined with the dependency configuration on the second LOV attribute - would then cause the second LOV to update using the view accessor to map the value from the first attribute into the appropriate bind variable on the second LOVs view criteria.
In my original post - I had mentioned that I setup the view accessor but didn't give much detail -- iss there some other method for referencing the parent attribute in the dependent LOV bind variable?