I have a read-only search view and a number of read-only LOV views configured in ADF BC (18.104.22.168.0).
I am building a search form (using af:query) and have a number of dependent / cascading LOVs configured and associated with attributes within the search view.
Based on the forum posts and documentation I have read - I have configured:
Under Attributes within the search view:
- Under "List of Values" configured the appropriate LOV
- Under "UI Hints" setup the attributes that have the cascading LOVs associated with them to have "Auto Submit" set to True on the UI Hints tab for the attribute.
- Under "Dependencies", added the attributes that the LOV is dependent on
Under View Accessors
- For each LOV, edit the view accessor to associate the appropriate attributes to the bind variables
When I select a value within the first LOV in the af:query region, the other List of Values drop downs do not seem to update.
When I perform the search by clicking on the search button - the results are displayed and the dependent list of values do seem to have the updated list of values based on the criteria.
Is there a way that I can get the dependent LOVs to update at the time that a value is selected within the master LOV, rather than needing to wait for the search to happen?
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.
Hi, - 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?