Very imporant new feature for me - possibility to define multiple LOV's per one attribute. Previously it was possible to have only one LOV defined in Model layer per attribute. In this post I will describe how it works, based on mentioned Steve Muench presentation, and will publish sample application I have developed - LOV_Multiple.zip. You will not be able to run this sample in TP4, only in production when it will be available (I hope very soon).
My sample is based on HR schema, it contains one main View object - EmployeesView and two read-only View objects for LOV's - DepartmentsView and DepartmentsEuropeView. Those two LOV's are based on different SQL statements:
With multiple LOV's per attribute feature, we can use now two or more View objects with different SQL statements for the same attribute. For example, basic SQL statment in DepartmentsView, returns all departments:
And SQL statment in DepartmentsEuropeView, returns departments only from Europe:
Here is a sample screen, where you can see multiple LOV's per attribute defined:
I have defined in this sample, two LOV's for DepartmentId attribute - LOV_Department and LOV_Department_Europe. There is List of Values Switcher attribute defined - lovAttr. This attribute returns LOV name to be used, I have created it as Transient attribute in Employees View object. In its getter method I'm doing a check - if current region is Europe I'm using LOV only with European departments, otherwise default LOV with all departments is used:
On runtime, if employee is based in European department - DepartmentId LOV will use DepartmentsEuropeView and will list only departments from Europe:
In other case, default LOV will be used with all available departments listed:
Hi.
ReplyDeleteNice new 11g feature. And what about bind variable in the lov ? That wasn't working in tp4.
Hi,
ReplyDeleteWhat you mean by bind variable in the LOV?
Regards,
Andrejus
Well, the lov is a view object, right ? So you can have a bind variable in the query and put the value at runtime or programactily.
ReplyDeleteIt didn't work with tp4.
That's what I meant :)
Regards
I have tried to use bind variable with LOV in cascading LOV. It was working, so I assume it works :)
ReplyDeleteAndrejus
I cannot seem to get it to call my switcher method. I get no errors, just never gets called. When I set my default to my non-standard list, I still get the standard list. It seems like it is never using this functionality. Any ideas?
ReplyDeleteHave you tried to run my sample app?
ReplyDeleteRegards,
Andrej
I was trying to do it in my backing bean instead of the row impl!
ReplyDeleteFYI - The default functionality does not appear to be based on which item is selected as default, but instead, it is always the first item in the list.
ReplyDeleteit doesn't work here too, only default LOV That shown
ReplyDeletethanks
It works for me...
ReplyDeleteWhat exactly not working for you?
Andrejus
hello Andrejus,
ReplyDeletewhen I try to change DeparmentId UIHint to ChoiceList instead of input list of value and use Employee view as ADF form not a table, i noticed that DepartmentId using LOV compatible with first row switcher flag
Hope to hear from you soon
Thanks
Andrejus el ejemplo me funciona pero cuando en una lista tengo nombre la LOV y lo cambio me trae la informacion del criterio de busqueda bien, pero si la vuelvo a cambiar me cambia el criterio de busqueda pero me deja mapeado los campos de LOV anterior en la tabla del resultado
ReplyDelete