Two Way Cascading LOV

Hi I have a new requirement where the LOV Components are interdependent on each other
for example I have master LOV and Child LOV ( 1: n Relationship)
If I have a Master LOV value say M1 then Child LOV values should be queried based on the value selected in MasterLOV. (Master->Child)
also if the user Directly goes to ChildLOV and selects a value say Child1M1 then the Master LOV should be defaulted to M1. (Child->Master)
Hope I was able to put my issue clearly. Please help me with any helpful How to Links or steps to achieve this.
Thanks
TK

As I understand, this cannot be done declarative-ly. But can be pro-grammatically.
Depicting the scenario specified with sample use case:
DEPARTMENTS EMPLOYEES
D1 ................... E1
D1 ................... E2
D1 ................... E3
D2 ................... E4
D2 ................... E5
1) Build LOV's based on all departments & all employees and use them selectOneChoice components.
2) Whenever the user selects/changes a department through the department LOV, have a valueChangeListener that will filter employees for the particular department. A View Criteria has to be executed on the employees - in order to filter.
3) Whenever the user selects a employee, In the valueChangeListener, identify the department for the selected employee and ensure that the department LOV has the current selected item as that of the current department of the selected employee.
For 2) and 3) to work, we need to ensure that PPR is defined properly.
Please let know, if you need any more inputs regarding the same.
Thanks,
Navaneeth

Similar Messages

Cascading LoVs in Apex 4 based on a shuttle box

I've set up cascading LoVs based on a shuttle box. When values are moved to the right-hand side of the shuttle box, the cascaded LoV items have their existing values cleared.
Is this a bug? Is there a fix or a workaround?

Hi again,
I made an unconditional process, sequence 1, but the only
thing working is the :P11_message is filled.
BEGIN
htp.prn('<script>alert(''Two is more then one'', Ok)</script>');
htp.prn('<script language="JavaScript" type="text/javascript">alert(''TEST'')</script>');
htp.p('<script>alert(''Two is more then one'', Ok)</script>');
htp.p('<script language="JavaScript" type="text/javascript">alert(''TEST'')</script>');
htp.p ('javascript:confirmDelete(htmldb_delete_message,''TEST'');');
htp.prn ('javascript:confirmDelete(htmldb_delete_message,''TEST'');');
htp.print ('javascript:confirmDelete(htmldb_delete_message,''TEST'');');
htp.p('TEST');
:P11_MESSAGE := 'TEST';
end;
Does any one have more suggestions.
Hugo

Cascading lovs in Jdeveloper R2

on Jdev R2.
I was doing several different Test with Jdev R2 regarding to cascading Lov and lovs components.
here are results.
lets split them in two flavors.
I. Forms.
a) cascading lovs works fine only if you use : input text item with lovs. (this one works fine even if you do not set autosubmit on the master and partial trigger on dependent lovs, .......cool)
b) if you choose selectOneChoise, "what is really nice for short list" it does not work. not even if you set autosubmit and partial trigger.
II. af:table
a) on editing mode: editAll
* using input text with lov works (you do not need to set autosubmit/partial triggers) but every time when you select a value from a list, an ugly error araise saying : field1 is required. field2 is required...to all require attributes (you can work after click)
* using selectOneChoise did not work. after you select the first lov the next lov is surrounded by red square and never get refreshed.
b) on editing mode: clickToEdit :
this is really cool and fast, but cascading lovs does not work at all. not even input text with lovs
has anybody any feedback/workaround/idea on this one, or should we wait until these bug get fixed, hopefully in the new release.
also I was wondering what is the best approuch to execute some java code on load/unload.?
thank you for any help.
Luis

to call java on load use af:clientlistener along with af:serverlistener.. use the type as load
http://blogs.oracle.com/jdevotnharvest/entry/how-to_call_server_side_java_from_javascript
or use the beforephase and afterphase property of f:view, refer navaneeth code here
popup on page load using managed bean, using jdev-11.4
use af:document's onunload property for unloading event and java calls

How to prevent apex 4.0 shuttle cleared by cascading LOV setting?

I have a shuttle control for choosing a list of database users populated from a child table by an On Load - After Header process, which then repopulates the child table in an On Submit - After Computations and Validations process. Work fine.
I then set the shuttle's Cascading LOV Parent Item(s) to a text item that could be used for filtering the shuttle's LOV, and revised the LOV SQL to a) use the filter and b) include items stored in the child table, i.e.:
select username as dv, username as rv
from all_users
where username like upper(:P5_USERSFILTER) || '%'
union
select username, username
from user_grouping_users
where groupid = :P5_GROUPID
order by 1
Unfortunately, when the filter value changes (P5_USERSFILTER), the state of shuttle (as set in my On Load - After Header process) is cleared. The values from the child table are properly included in the LOV, but they are no longer selected -- so the appear in the left-hand list as candidate values but not in the right-hand list as selected values. Additionally, any items selected in the shuttle before changing the value of the LOV Parent (:P5_USERSFILTER) are no longer selected.
Is there a way to prevent the selections of a Cascading LOV item from being cleared when the parent item is reset?
Note, I've specified 'No' for Optimize Refresh, and 'P5_USERS' for Page Items to Submit and 'Yes' for Display Extra Values (which in general does not seem to have any affect on a shuttle LOV)

Hallo all!
I got a similar situation: a text item that filters the left side of an shuttle item (P11_IAG_ENUM), but the right side should stay the same - independet from the text item, where search-phrases are entered.
So I tired with your example - thanks for that - but I changed the code that I only have one collection 'P11_IAG_VALUES' ... but right side seems to be still dependend from the search item. I also deleted the "set value" action of the "save current selection"-dynamic-action, because I supposed it's not needed.
Here is my "save current selection"-dynamic-action:
DECLARE
c_collection CONSTANT VARCHAR2(30) := 'P11_IAG_VALUES';
l_seq_id NUMBER;
BEGIN
IF NOT apex_collection.collection_exists(c_collection) THEN
apex_collection.create_collection(c_collection);
END IF;
SELECT MIN(seq_id)
INTO l_seq_id
FROM apex_collections
WHERE collection_name = c_collection
IF l_seq_id IS NULL THEN
apex_collection.add_member (
p_collection_name => c_collection,
p_c001 => :P11_IAG_ENUM );
ELSE
apex_collection.update_member (
p_collection_name => c_collection,
p_seq => l_seq_id,
p_c001 => :P11_IAG_ENUM );
END IF;
COMMIT;
END;
... and the "restore old selection"-dynamic-action:
DECLARE
l_selected_iag VARCHAR2(32767);
BEGIN
SELECT c001
INTO l_selected_iag
FROM apex_collections
WHERE collection_name='P11_IAG_VALUES'
RETURN l_selected_iag;
EXCEPTION
WHEN NO_DATA_FOUND THEN
RETURN NULL;
END;
Where is my error in reasoning?
(Meanwhile I try to create an example application...)
[Edit: I got problems to acces my workspace, try to reset my password --> error, even try to find my workspace -->error .... everytime the same; I'll try it later again, but hoping that anyone can help me without example application]
Edited by: kc7 on 10.09.2010 09:20
[Edit II: I finally created a example-application: *http://apex.oracle.com/pls/apex/f?p=30216*
workspace: kc7
user: dummy
pwd: doll
Edited by: kc7 on 10.09.2010 12:28

Apex 4.2.1 - mobile theme display bugs and Cascading LOV bug

I've setup a test at http://apex.oracle.com/pls/apex/f?p=35331 - username/password is test/test
Simple page to show some issues I'm running into. Wondering if work-arounds exist or if a patch would be available before we'd go live.
First and second issue are the same I believe. So - a normal text box (label1) looks fine. But, Label2 is a Display only item and Label3 is a read-only select list item. As you can see - both of the values appear smack dab right beside the label and not in line with the other fields. It's totally ugly and not usable as is. I've tried to move this over, but the label goes with it. I can see no way of doing it, but wondering if there's some hack I can put in to solve it...
The last issues is with a cascading LOV. Simple table setup. Static on the first, the second a simple query that filters on the first. If you set the select list to Value Required and not to display null values - then when you click on the Second List button - it just hangs. The page is unusable. I suspect this has to do with the null or something. But - doesn't appear to matter if anything is chosen. Note - if the list is large - which I think then uses a different UI control, this is fine. Only when one of the lists is small does the issue reproduce.
Any workarounds or fixes? Any ideas?
Thanks

Hi,
I would suggest to not mix different questions and a thread for each of them. Makes it easier for others to follow.
About your problem with the cascading LOVs, it appears that this is/was a bug in jQuery Mobile which we use under the hood. I was able to reproduce the problem with APEX 4.2.1 using jQM 1.2.0, but was not able to reproduce it with APEX 5.0 which will use jQM 1.3.0RC1 or higher. The problem occurs if a select list is empty.
There are different workarounds available:
1) set the attribute "HTML Form Element Attributes" of P1_CLOV_2 to data-native-menu="false"or
2) set the attribute "Display Null Value" of P1_CLOV_2 to Yes and "Null Display Value" to - select - (or something similar). The "Value Required" = Yes will still guarantee that a value has to be picked. Having the extra null entry will guarantee that the select list always contains an entry, that seems to workaround the bug in jQuery Mobile.
I have filed bug 16355963 - jquery mobile: empty select list causes javascript error
to track that this is definitely fixed in APEX 5.0.
Regards
Patrick
My Blog: http://www.inside-oracle-apex.com
APEX Plug-Ins: http://apex.oracle.com/plugins
Twitter: http://www.twitter.com/patrickwolf

Af:query component with cascading Lov's

Hi All,
I have Cascading LOV's model setup in Business Components and they work fine in a form or table
but they are not working inside af:query component as there is no autoSubmit attribute on the query component itself
can someone help me to resolve this
Thanks in Advance

I have found a way
using bindings attribute of the query component it was able to go to backing bean on any LOV change in there we need to manually refresh the bindings then it works

Cascading LOV in a Query panel (af:query)

Hi
I have a requirement to implement few Cascading LOV's in a Query panel. I have created the VO's for the LOV's with bind variable and view criteria and linked them. It works for the BC viewer. But to enable in the ADF UI, the partial trigger needs to be enabled on individual field. And the af:query encapsulates the fields and they are not exposed. Can someone help me with a solution or a pointer
Many thanks

Thanks for the pointer
Well I followed the the steps, and implemented the same for two LOV's. I'm getting "Server Exception during PPR, #1". Would be able to identify where I'm going wrong please.
FYI: I'm using a UI template that is stripped won from Oracles Dynamic tab template
1. parent LOV
<?xml version="1.0" encoding="windows-1252" ?>
<!DOCTYPE ViewObject SYSTEM "jbo_03_01.dtd">

<ViewObject
xmlns="http://xmlns.oracle.com/bc4j"
Name="QcChiptypeVViewRO"
Version="11.1.1.56.60"
BindingStyle="OracleName"
CustomQuery="true"
RowClass="com.qualcomm.qdt.fwk.model.QdtViewRowImpl"
ComponentClass="com.qualcomm.qdt.fwk.model.QdtViewObjectImpl"
DefClass="com.qualcomm.qdt.fwk.model.QdtViewDefImpl"
PageIterMode="Full"
UseGlueCode="false">
<DesignTime>
<Attr Name="_codeGenFlag2" Value="Access|VarAccess"/>
<Attr Name="_isExpertMode" Value="true"/>
</DesignTime>
<SQLQuery>
<![CDATA[SELECT QcChiptypeV.CHIPTYPE
FROM QC_CHIPTYPE_V QcChiptypeV]]>
</SQLQuery>
<ViewAttribute
Name="Chiptype"
IsUpdateable="false"
IsPersistent="false"
PrecisionRule="true"
Precision="42"
Type="java.lang.String"
ColumnType="VARCHAR2"
AliasName="CHIPTYPE"
Expression="CHIPTYPE"
SQLType="VARCHAR">
<DesignTime>
<Attr Name="_DisplaySize" Value="42"/>
</DesignTime>
</ViewAttribute>
</ViewObject>
2. Child LOV
<?xml version="1.0" encoding="windows-1252" ?>
<!DOCTYPE ViewObject SYSTEM "jbo_03_01.dtd">

<ViewObject
xmlns="http://xmlns.oracle.com/bc4j"
Name="QcMcnVViewRO"
Version="11.1.1.56.60"
BindingStyle="OracleName"
CustomQuery="true"
RowClass="com.qualcomm.qdt.fwk.model.QdtViewRowImpl"
ComponentClass="com.qualcomm.qdt.fwk.model.QdtViewObjectImpl"
DefClass="com.qualcomm.qdt.fwk.model.QdtViewDefImpl"
PageIterMode="Full"
UseGlueCode="false">
<DesignTime>
<Attr Name="_codeGenFlag2" Value="Access|VarAccess"/>
<Attr Name="_isExpertMode" Value="true"/>
</DesignTime>
<Variable
Name="chiptype"
Kind="viewcriteria"
Type="java.lang.String"/>
<ViewAccessor
Name="QcChiptypeVViewRO1"
ViewObjectName="com.qualcomm.qdt.model.lov.QcChiptypeVViewRO"
RowLevelBinds="true"/>
<SQLQuery>
<![CDATA[SELECT QcMcnV.MCN,
QcMcnV.CHIPTYPE
FROM QC_MCN_V QcMcnV]]>
</SQLQuery>
<ViewAttribute
Name="Mcn"
IsUpdateable="false"
IsPersistent="false"
PrecisionRule="true"
Precision="20"
Type="java.lang.String"
ColumnType="VARCHAR2"
AliasName="MCN"
Expression="MCN"
SQLType="VARCHAR">
<DesignTime>
<Attr Name="_DisplaySize" Value="20"/>
</DesignTime>
<Dependencies>
<Item
Value="Chiptype"/>
</Dependencies>
</ViewAttribute>
<ViewAttribute
Name="Chiptype"
IsUpdateable="false"
IsPersistent="false"
PrecisionRule="true"
Precision="42"
Type="java.lang.String"
ColumnType="VARCHAR2"
AliasName="CHIPTYPE"
Expression="CHIPTYPE"
SQLType="VARCHAR">
<DesignTime>
<Attr Name="_DisplaySize" Value="42"/>
</DesignTime>
</ViewAttribute>
<ViewCriteria
Name="QcMcnVViewROCriteriaChiptype"
ViewObjectName="com.qualcomm.qdt.model.lov.QcMcnVViewRO"
Conjunction="AND">
<Properties>
<CustomProperties>
<Property
Name="displayOperators"
Value="InAdvancedMode"/>
<Property
Name="autoExecute"
Value="true"/>
<Property
Name="allowConjunctionOverride"
Value="true"/>
<Property
Name="showInList"
Value="true"/>
<Property
Name="mode"
Value="Basic"/>
</CustomProperties>
</Properties>
<ViewCriteriaRow
Name="vcrow5"
UpperColumns="1">
<ViewCriteriaItem
Name="QcMcnVViewROCriteria_vcrow5_Chiptype"
ViewAttribute="Chiptype"
Operator="="
Conjunction="AND"
Value=":chiptype"
IsBindVarValue="true"
Required="Optional"/>
</ViewCriteriaRow>
</ViewCriteria>
</ViewObject>
3. JSF page
<?xml version='1.0' encoding='UTF-8'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
<jsp:directive.page contentType="text/html;charset=UTF-8"/>
<f:view>
<af:document id="d1">
<af:messages id="m1"/>
<af:form id="f1">
<af:pageTemplate viewId="/oracle/ui/pattern/dynamicShell/dynamicTabShell.jspx"
value="#{bindings.pageTemplateBinding}" id="pt1">
<f:facet name="copyright">
<af:outputText value="2010 Qualcomm Inc. All Rights Reserved."
id="ot10"/>
</f:facet>
<f:facet name="about">
<af:navigationPane id="np3" hint="buttons">
<af:commandNavigationItem text="About" id="cni5"/>
<af:commandNavigationItem text="Privacy" id="cni6"/>
</af:navigationPane>
</f:facet>
<f:facet name="navigation">
<af:panelAccordion id="pa1">
<af:showDetailItem text=" Asset Details" id="sdi1">
<af:panelGroupLayout layout="vertical" id="pgl1">
<af:panelHeader text=" " id="ph1">
<af:query id="qryId1"
headerText="Search Criteria (Use % as wildcard)" disclosed="true"
value="#{bindings.ImplicitViewCriteriaQuery.queryDescriptor}"
model="#{bindings.ImplicitViewCriteriaQuery.queryModel}"
queryListener="#{bindings.ImplicitViewCriteriaQuery.processQuery}"
queryOperationListener="#{bindings.ImplicitViewCriteriaQuery.processQueryOperation}"
saveQueryMode="hidden"/>
</af:panelHeader>
</af:panelGroupLayout>
</af:showDetailItem>
<af:showDetailItem text="More Info" id="sdi2"/>
</af:panelAccordion>
</f:facet>
<f:facet name="globalLinks">
<af:navigationPane id="np2" hint="buttons"
inlineStyle="text-align:right;">
<af:commandNavigationItem text="Help" id="cni4" action="noop"/>
<af:commandNavigationItem text="Sign out"
id="commandNavigationItem1"
action="noop"/>
</af:navigationPane>
</f:facet>
<f:facet name="status"/>
<f:facet name="globalToolbar"/>
<f:facet name="globalSearch"/>
<f:facet name="globalTabs">
<af:navigationPane id="np1">
<af:commandNavigationItem text="Device Query/Update" id="cni1"
selected="true" partialSubmit="false"/>
<af:commandNavigationItem text="Asset Return" id="cni3"
action="dummy" rendered="false"/>
</af:navigationPane>
</f:facet>
<f:facet name="welcome">
<af:panelSplitter id="ps1" orientation="vertical">
<f:facet name="first">
<af:panelCollection id="pc1" defaultToolbarItemDisplay="icon">
<f:facet name="menus">
<af:menu text="Options" id="m2" rendered="false">
<af:commandMenuItem text="Printable Page" id="cmi2">
<af:showPrintablePageBehavior/>
</af:commandMenuItem>
<af:commandMenuItem text="Download" id="commandMenuItem1">
<af:exportCollectionActionListener exportedId="t2"
type="excelHTML"
title="Asset Details"/>
</af:commandMenuItem>
</af:menu>
</f:facet>
<f:facet name="toolbar">
<af:toolbar id="t1">
<af:commandToolbarButton id="ctb1"
hoverIcon="/images/view_image.gif"
text="Export to Excel">
<af:exportCollectionActionListener exportedId="t2"
type="excelHTML"
title="Asset Details"/>
</af:commandToolbarButton>
</af:toolbar>
</f:facet>
<f:facet name="statusbar"/>
<af:table value="#{bindings.QcDeviceTrackingVO1.collectionModel}"
var="row"
rows="#{bindings.QcDeviceTrackingVO1.rangeSize}"
emptyText="#{bindings.QcDeviceTrackingVO1.viewable ? 'No data to display.' : 'Access Denied.'}"
fetchSize="#{bindings.QcDeviceTrackingVO1.rangeSize}"
rowBandingInterval="0"
filterModel="#{bindings.ImplicitViewCriteriaQuery.queryDescriptor}"
queryListener="#{bindings.ImplicitViewCriteriaQuery.processQuery}"
filterVisible="true" varStatus="vs"
selectedRowKeys="#{bindings.QcDeviceTrackingVO1.collectionModel.selectedRow}"
selectionListener="#{bindings.QcDeviceTrackingVO1.collectionModel.makeCurrent}"
rowSelection="single" id="t2"
columnSelection="single"
partialTriggers=":::ph1 :::qryId1">
<af:column sortProperty="Serialnum" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Serialnum.label}"
id="c28" width="103">
<af:outputText value="#{row.Serialnum}" id="ot17"/>
</af:column>
<af:column sortProperty="Assettag" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Assettag.label}"
id="c7" width="107">
<af:outputText value="#{row.Assettag}" id="ot24"/>
</af:column>
<af:column sortProperty="Chiptype" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Chiptype.label}"
id="c18" width="26">
<af:outputText value="#{row.Chiptype}" id="ot27"/>
</af:column>
<af:column sortProperty="Mcn" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Mcn.label}"
id="c11">
<af:outputText value="#{row.Mcn}" id="ot13"/>
</af:column>
<af:column sortProperty="Mcnrev" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Mcnrev.label}"
id="c8">
<af:outputText value="#{row.Mcnrev}" id="ot3"/>
</af:column>
<af:column sortProperty="Assignedto" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Assignedto.label}"
id="c15">
<af:outputText value="#{row.Assignedto}" id="ot32"/>
</af:column>
<af:column sortProperty="Location" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Location.label}"
id="c24">
<af:outputText value="#{row.Location}" id="ot19"/>
</af:column>
<af:column sortProperty="Locationfullname" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Locationfullname.label}"
id="c14">
<af:outputText value="#{row.Locationfullname}" id="ot26"/>
</af:column>
<af:column sortProperty="Locationtype" filterable="true"
sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Locationtype.label}"
id="c13">
<af:outputText value="#{row.Locationtype}" id="ot28"/>
</af:column>
<af:column sortProperty="Description" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Description.label}"
id="c21">
<af:outputText value="#{row.Description}" id="ot22"/>
</af:column>
<af:column sortProperty="Assignment" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Assignment.label}"
id="c30">
<af:outputText value="#{row.Assignment}" id="ot34">
<af:convertNumber groupingUsed="false"
pattern="#{bindings.QcDeviceTrackingVO1.hints.Assignment.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Createddate" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Createddate.label}"
id="c1">
<af:outputText value="#{row.Createddate}" id="ot15">
<af:convertDateTime pattern="#{bindings.QcDeviceTrackingVO1.hints.Createddate.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Lastid" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Lastid.label}"
id="c33">
<af:outputText value="#{row.Lastid}" id="ot9">
<af:convertNumber groupingUsed="false"
pattern="#{bindings.QcDeviceTrackingVO1.hints.Lastid.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Lportfolioitemid" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Lportfolioitemid.label}"
id="c23">
<af:outputText value="#{row.Lportfolioitemid}" id="ot23">
<af:convertNumber groupingUsed="false"
pattern="#{bindings.QcDeviceTrackingVO1.hints.Lportfolioitemid.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Lkeycontactid" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Lkeycontactid.label}"
id="c4">
<af:outputText value="#{row.Lkeycontactid}" id="ot11">
<af:convertNumber groupingUsed="false"
pattern="#{bindings.QcDeviceTrackingVO1.hints.Lkeycontactid.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Fullname" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Fullname.label}"
id="c22">
<af:outputText value="#{row.Fullname}" id="ot6"/>
</af:column>
<af:column sortProperty="Status" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Status.label}"
id="c16">
<af:outputText value="#{row.Status}" id="ot21"/>
</af:column>
<af:column sortProperty="Qcemployeenumber" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Qcemployeenumber.label}"
id="c6">
<af:outputText value="#{row.Qcemployeenumber}" id="ot33">
<af:convertNumber groupingUsed="false"
pattern="#{bindings.QcDeviceTrackingVO1.hints.Qcemployeenumber.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Field3" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Field3.label}"
id="c12">
<af:outputText value="#{row.Field3}" id="ot18"/>
</af:column>
<af:column sortProperty="Empdeptfullname" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Empdeptfullname.label}"
id="c27">
<af:outputText value="#{row.Empdeptfullname}" id="ot4"/>
</af:column>
<af:column sortProperty="Comments" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Comments.label}"
id="c10">
<af:outputText value="#{row.Comments}" id="ot16"/>
</af:column>
<af:column sortProperty="Builtby" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Builtby.label}"
id="c19">
<af:outputText value="#{row.Builtby}" id="ot20"/>
</af:column>
<af:column sortProperty="Mesbuild" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Mesbuild.label}"
id="c31">
<af:outputText value="#{row.Mesbuild}" id="ot2"/>
</af:column>
<af:column sortProperty="Esn" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Esn.label}"
id="c26">
<af:outputText value="#{row.Esn}" id="ot31"/>
</af:column>
<af:column sortProperty="Imei" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Imei.label}"
id="c17">
<af:outputText value="#{row.Imei}" id="ot29"/>
</af:column>
<af:column sortProperty="Macaddress" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Macaddress.label}"
id="c32">
<af:outputText value="#{row.Macaddress}" id="ot1"/>
</af:column>
<af:column sortProperty="Brf" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Brf.label}"
id="c25">
<af:outputText value="#{row.Brf}" id="ot8"/>
</af:column>
<af:column sortProperty="Brfrev" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Brfrev.label}"
id="c3">
<af:outputText value="#{row.Brfrev}" id="ot25"/>
</af:column>
<af:column sortProperty="Dacquisition" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Dacquisition.label}"
id="c29">
<af:outputText value="#{row.Dacquisition}" id="ot7">
<af:convertDateTime pattern="#{bindings.QcDeviceTrackingVO1.hints.Dacquisition.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Datqcmainttermdate" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Datqcmainttermdate.label}"
id="c2">
<af:outputText value="#{row.Datqcmainttermdate}"
id="ot30">
<af:convertDateTime pattern="#{bindings.QcDeviceTrackingVO1.hints.Datqcmainttermdate.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Datqcissueddate" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Datqcissueddate.label}"
id="c5">
<af:outputText value="#{row.Datqcissueddate}" id="ot5">
<af:convertDateTime pattern="#{bindings.QcDeviceTrackingVO1.hints.Datqcissueddate.format}"/>
</af:outputText>
</af:column>
<af:column sortProperty="Itlqciteclass" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.Itlqciteclass.label}"
id="c20">
<af:outputText value="#{row.Itlqciteclass}" id="ot14"/>
</af:column>
<af:column sortProperty="RowID" sortable="true"
headerText="#{bindings.QcDeviceTrackingVO1.hints.RowID.label}"
id="c9">
<af:outputText value="#{row.RowID}" id="ot12"/>
</af:column>
</af:table>
</af:panelCollection>
</f:facet>
<f:facet name="second">
<af:panelTabbed id="pt2">
<af:showDetailItem text="Update Attributes" id="sdi3"
stretchChildren="first"/>
</af:panelTabbed>
</f:facet>
</af:panelSplitter>
</f:facet>
<f:facet name="innerToolbar"/>
<f:attribute name="brandingTitle" value="ITE Device Tracking System"/>
<f:attribute name="navSplitterPosition" value="450"/>
</af:pageTemplate>
</af:form>
</af:document>
</f:view>
</jsp:root>

Are cascading LOVs possible in af:query?

Is it possible to have two or more cascading LOVs in an af:query area based on a view criteria?
I'm having some trouble with dependant (child) LOVs: they filter correctly but return nothing to the field from which were launched.
I can attach a code snippet if necessary
Thanks
JDeveloper 11.1.1.3.0 with ADF BC
Anybody has ever tried it?
Edited by: Marge on 02-sep-2010 23:17

Is it possible to have two or more cascading LOVs in an af:query area based on a view criteria?Yes, it is possible
There might be something wrong in the configuration, Can you upload the sample app so that it will be easy to figure out the issue.
Sireesha

Cascading LOV behavior

Hi,
I have created a Cascading LOV for Employee-> Dept No and unchecked Hierarchical View in u201CCreate Cascading List of Valuesu201D option.
Then I created a Webi report and applied u201CDept Nou201D as Prompt with LOV option enabled.
When I refresh the report it is displaying two prompts, one for Dept No and other for Employee.
I selected the value for Dept No. Then accordingly Employee prompt is also filtered based on Dept No, and I selected one employee number.
When I view the report after specifying prompt values, it is showing all the employees under that Dept, but I would like to see only for the Dept No and Employee selected in the prompt window.
When I check the Report Query, I find a where condition only on Dept No, and not on Employee.
Is this the kind of behavior one would expect in BOXI 3.1. Please let me know.
Thank you.

Hi Mohamed,
The Employee parameter should appear only once. You might have done some thing additional.
Had you tried to create any cascading LoVs? If yes then delete it. The definition of the objects should be as given below.
Please check the definitions of the objects as:
Employee: tobe dragged in the query
Select: Table Emp.Name
Lov Employee
Select: Table Emp.Name
Where: @Select(Table Dept.\Name) In @prompt('Select Employee','A','Table Dept.\Name,multi,constrained)
Dept
Select: Table Dept.Name
Prompt (Predefined Condition): to be dragged in the query
@Select(Emp\Name) InList @prompt('Select Employee','A','LoVs\Lov Employee',multi,constrained)
Regards,
Rohit
Edited by: rohit12 on Mar 9, 2010 5:54 AM

Cascade LOV for Multi Row Report

Hi,
Is there a way to support cascaded LOV's in a report, where there are multiple rows?
Thanks

Why don't you try this
SELECT    apex_item.hidden (10, tr.seq)
       || apex_item.checkbox (20,
                              tr.seq,
                              'onchange="spCheckChange(this);"',
                              :f500_request_list,
                              'f20_' || '#ROWNUM#'
                             ) "Is Requested?",
       apex_item.select_list_from_lov_xl (30,
                                          to_room_seq,
                                          'ROOMS_LOV',
                                          'NO',
                                          NULL,
                                          NULL,
                                          'f30_' || '#ROWNUM#',
                                          NULL,
                                          'NO'
FROM ts_assets ta, ts_reqs tr?
Denes Kubicek
http://deneskubicek.blogspot.com/
http://www.opal-consulting.de/training
http://apex.oracle.com/pls/otn/f?p=31517:1
------------------------------------------------------------------------------

Cascading LOV without setting autosubmit to be "true"

Does anyone know how to make the cascading LOV works on a JSF page without setting the autosubmit to be true?
Here is my usecase: An entity X has attribute A, B, C, in which the LOV of attribute C is dependent on A; however, all A, B, C are mandatory on the database constraint level. So, if I set the autosubmit to be true for A in order to make B knows the changes on A, the Validation Error message will be pop up saying that attributes A, B, C are needed for entity X.
Therefore, is there a way to make C knows the changes of A without setting the autosubmit of A to be true?
Thanks much,
Jinyan

Hi Predja,
After I set the immediate of A to be true, on the page, after I selected the value of A, the field of C does not have a LOV showing up.

JDev: af:query cascade LOVs

Hi,
I have question about cascade LOVs inside af:query component (generated automatically via viewCriteria).
Is it possible to have two LOVs (master slave relation), in first user selects department, and then he gets all employees which are
in selected department in second ? (search must be possible only by department)
Regards, Rok Kogovšek

Hi,
I managed to made LOV behavior in cascading fashion but i have another problem, form is refreshed when user click on search button.
Is it possible to set partial trigger of first LOV to refresh second one or to refresh complete form on value change.
Regards Rok Kogovšek

Resetting cascading LOVs

Hi.
I have a problem (who doesn't?). Picture this:
I have 5 cascading LOVs. Each LOV includes a null value for "Not Defined", which is produced like this:
select trim(name), value
from table
where column = :VAR_FROM_PREVIOUS_LOV
union all
select ' Not defined', null
from dual
order by 1
Notice that the value ' Not defined' has a leading blank and will always be the one displayed in the LOV before a selection is made because that leading blank will sort before the other values. Each LOV is driven from a different table.
Each LOV is a "Select with submit" with Source type "Only when current value in session state is null".
Branching to same page is in place for the requests associated with these LOVs.
This works fine, apart from one nasty detail:
Imagine you set LOV1. LOV2 has now the values associated with the selection of LOV1, right?
You then proceed selecting LOV2, LOV3, LOV4 and LOV5 in sequence. Ok, it works fine so far.
But now the user changes his/her mind, and resets the value in LOV2. One would expect that LOV3 would now contain the values associated with the new value in LOV2. Well, that is, in fact, the case. But since LOV3 is showing ' Not defined', one would also expect LOV4 and LOV5 to be reset with the only value of 'Not defined'. Well, it doesn't happen! LOV4 and LOV5 still carry the previous selection, which is now unrelated with the selection of LOVs 1,2 and 3.
The thing acts as if all LOVs were calculated at the same time on submit, instead of being reset in sequence, one after the other, which is what I hoped would happen, following their sequence number.
Does anyone have any way around this behaviour?
Thanks,
Paulo Terca

Hi, Scott.
Thanks for replying. I realize my description may have been a bit confusing.
I'll give an example: Imagine several tables, each one a detail of the previous, like, for instance:
Regions
Countries
Country_regions
Cities
Suppliers
Now picture 5 LOVs, one for each attribute. Only the "Regions" LOV has values. When you select a Region (e.g., EMEA), the LOV for Countries gets populated. You now select a country, and the LOV for Country_regions gets populated. Once you get to the city, you will get a list of suppliers from that city. You select a supplier and get the details of that supplier.
Now the things is: imagine you are satisfied with your search and want to check on another supplier that lives in China. You want to select "Asia" from the first LOV and expect that the LOV for countries will be populated with all asian countries, but all other LOVs will be reset to a state of emptyness, right? You don't want to be seeing "Asia" and still see "Paris" for the city and whatever supplier was previously selected.
So, what I did was that in each LOV I would have a SELECT that would have a WHERE clause dependent of an attribute taken from the previous LOV:
LOV1: select name, id from regions
LOV2: select name, id from countries where region_id = :P10_REGIONS
LOV3: select name, id from country_regions where country_id = :P10_COUNTRIES
LOV4: select name, id from cities where country_region_id = :P10_COUNTRY_REGIONS
LOV5: select name, id from suppliers where city_id = :P10_CITY
All selects have submit. Well, if you try this, you'll see that after making the first run through the LOVS, when you try a different selection on the first, the 4th and 5th will still have the previous city and supplier.
I managed to solve this problem in the following way:
LOV1: select name, id from regions
LOV2: select name, id from countries where region_id = :P10_REGIONS
LOV3: select name, id from country_regions where region_id = :P10_REGIONS and country_id = :P10_COUNTRIES
LOV4: select name, id from cities where region_id = :P10_REGIONS and country_id = :P10_COUNTRIES and country_region_id = :P10_COUNTRY_REGIONS
LOV5: select name, id from suppliers where region_id = :P10_REGIONS and country_id = :P10_COUNTRIES and country_region_id = :P10_COUNTRY_REGIONS and city_id = :P10_CITY
It's messier, but works.
Anyway, thanks again for your input.
Regards,
Paulo Terca

Unable to establish the two way communication with printer j110a

every thing is ok but during the printing or ink level checking this message displayed "unable to establish the two way communication with printer j110a" please reply soon?

Hard Reset – While printer is powered ON, pull the power cord from the printer then from the wall. After 30 seconds reconnect power to wall and printer. This will trigger a ‘dirty power up’ and restore the printer to a known good condition (if it is possible). No user settings are lost with a ‘hard reset’. This ‘Hard Reset’ is one of the most powerful tools to use when the printer hardware is not functioning properly! IF NOT RESOLVED, uninstall hp software & reinstall using latest hp software from hp website.
Although I am working on behalf of HP, I am speaking for myself and not for HP.
Love Kudos! If you feel my post has helped you please click the White Kudos! Star just below my name : )
If you feel my answer has fixed your problem please click 'Mark As Solution' and make it easier for others to find help quickly : )
Happy Troubleshooting : )

Cascading LOVs (v4) and retaining the child value

I've implemented the default delivered implementation in version 4 (4.0.2.00.07 to be exact) of cascading LOVs. Working fine except for one thing...after refresh of a child LOV, the previously selected value is wiped out even when it's still a valid value in the child LOV. If it's an invalid value, I can understand that it would be wiped out, but if it's still valid, I'd like it to be retained.
Example...let's say I have these two select-lists (parent and child).
P100_PARENT
P100_CHILD
P100 Child's SQL references P100_PARENT:
where b.child = NVL(a.parent,b.child)
Optimize refresh is also set to 'No' because I need the child to refresh to all children selections when parent is null.
In short, the parent is optional. If Parent is null, show all child options regardless of Parent. If Parent is defined, show only the child options for the parent.
So when parent is null, I get all child options (OK). I pick one.
If I go to parent and change it to a specific value that IS the parent of the child I chose, my expectation is the child select list should refresh (it does) but if my chosen value is still in the list, it should scroll to it and select it. Instead, it wipes it out.
To put some values into the example...
Let's say parent values are:
A
B
C
null
Let's say child values are numbers such that valid values are:
1 through 10 when parent is A
11 through 20 when parent is B
20 through 30 when parent is C
1 through 30 (any child value) when parent is null.
So I have a null parent LOV value and the child shows me 1 through 30 (OK). I pick 15.
I change the parent to 'B'. Child list refreshes (OK). But while 15 is still a valid value in the list, it is not selected again (my value is wiped out). I still want it to have '15' selected.
Any workaround? Is this a bug? Enhancement opportunity?

Hi Matt,
have you had a look at Skill Builders "Save Value on Cascade" dynamic action plug-in? See http://skillbuilders.com/oracle-apex/Application-Express-APEX-Consulting-Training.cfm?tab=free-plugin-downloads
Regards
Patrick
My Blog: http://www.inside-oracle-apex.com
APEX Plug-Ins: http://apex.oracle.com/plugins
Twitter: http://www.twitter.com/patrickwolf

Two Way Cascading LOV

Similar Messages

Maybe you are looking for