Skip to main content

LOV problem in a multi line edit list

JDeveloper 11.1.2.1

We where having problems with our LOV lookups in a multi table edit list.

Where scolling down on the lov with a substantial number of records the LOV list would just reflect Fetching Records... indefinitely.

For now I have bound the multi list LOV to another lov model I had on the page with the same LOV in and it works but I will put some more time in finding another solution to this at some time because I am going on holiday next week - awesome.

Example
Had the following LOV on the page

<af:inputListOfValues id="ilov1" popupTitle="Search and Select: #{bindings.EmployeeId.hints.label}"
  value="#{bindings.EmployeeId.inputValue}"
  label="#{bindings.EmployeeId.hints.label}"
  model="#{bindings.EmployeeId.listOfValuesModel}"
  required="#{bindings.EmployeeId.hints.mandatory}"
  columns="#{bindings.EmployeeId.hints.displayWidth}"
  shortDesc="#{bindings.EmployeeId.hints.tooltip}">
  <f:validator binding="#{bindings.EmployeeId.validator}"/>
  <af:convertNumber groupingUsed="false" pattern="#{bindings.EmployeeId.format}"/>
</af:inputListOfValues>

And this LOV was the problematic on in an editable table.

<af:inputListOfValues id="employeeIdId"
 popupTitle="Search and Select: #{bindings.JobHistoryView1.hints.EmployeeId.label}"
 value="#{row.bindings.EmployeeId.inputValue}"
 model="#{row.bindings.EmployeeId.listOfValuesModel}"
 required="#{bindings.JobHistoryView1.hints.EmployeeId.mandatory}"
 columns="#{bindings.JobHistoryView1.hints.EmployeeId.displayWidth}"
 shortDesc="#{bindings.JobHistoryView1.hints.EmployeeId.tooltip}">
  <f:validator binding="#{row.bindings.EmployeeId.validator}"/>
  <af:convertNumber groupingUsed="false"
    pattern="#{bindings.JobHistoryView1.hints.EmployeeId.format}"/>
</af:inputListOfValues>

So I endeded up with this for the problematic one:
<af:inputListOfValues id="employeeIdId"
 popupTitle="Search and Select: #{bindings.JobHistoryView1.hints.EmployeeId.label}"
 value="#{row.bindings.EmployeeId.inputValue}"
 model="#{bindings.EmployeeId.listOfValuesModel}"
 required="#{bindings.JobHistoryView1.hints.EmployeeId.mandatory}"
 columns="#{bindings.JobHistoryView1.hints.EmployeeId.displayWidth}"
 shortDesc="#{bindings.JobHistoryView1.hints.EmployeeId.tooltip}">
  <f:validator binding="#{row.bindings.EmployeeId.validator}"/>
  <af:convertNumber groupingUsed="false"
    pattern="#{bindings.JobHistoryView1.hints.EmployeeId.format}"/>
</af:inputListOfValues>

Comments

Popular posts from this blog

MANIFEST.MF merge JDeveloper for an executable jar

Goto your project > properties. Then click on deployment in the menu. Edit or add a jar deployment profile. Fill in the details under jar options (select Include manifest and give it a main class name) Also remember that the merge functionality only works with a BLANK line at the end of the merge file. REALLY this caught me. My merge file contents: Class-Path: commons-codec-1.3.jar [...empty line here CRLF...]

OJDeploy: Documentation for the tool

Real DOCS:  http://docs.oracle.com/cd/E26098_01/user.1112/e17455/deploying_apps.htm#OJDUG645 OJDeploy Documentation if you run it from the command line - I keep looking for this so I though I would post it here so I remeber. Oracle JDeveloper Deploy 11.1.2.1.0.6081 Copyright (c) 2003, 2010, Oracle and/or its affiliates. All rights reserved. Usage:   ojdeploy -profile <name> -workspace <jws> [ -project <name> ] [ <options> ]   ojdeploy -buildfile <ojbuild.xml> [ <options> ]   ojdeploy -buildfileschema Arguments:   -profile               the name of the Profile to deploy   -workspace      full path to the JDeveloper Workspace file(.jws)   -project              name of the JDeveloper Project within the .jws where the Profile can be...

JBO-25013: TooManyObjectsException

oracle.jbo.TooManyObjectsException: JBO-25013: Too many objects match the primary key oracle.jbo.Key[Key null ]. Ok so for you it may be trying to insert a duplicate record this should explain your problem (also check trigger they could be the cause.) NOTE: You can also try to create a new duplicate EO if you have a page with two VO's using the same EO. This could sort your problems. For me I needed to add a launch listener on my LOV and clear the cache of my vo. LOV <af:inputListOfValues id="NameId" popupTitle="#{bindings.Name.hints.label}" value="#{bindings.RolName1.inputValue}" label="#{bindings.RolName1.hints.label}" model="#{bindings.RolName1.listOfValuesModel}" required="#{bindings.RolName1.hints.mandatory}" columns="#{bindings.RolName1.hints.displayWidth}" shortDesc="#{bindings.RolName1.hints.tooltip}" launchPopupListener="#{backingBeanScope.backingBean.launchPop...