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

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...

ADF: LOV Description instead of code

I keep on forgetting how to do this so this is a note to self in terms I understand (ie pictures): Add the related entiy object to yours (in the example we are adding RegionEO(list of values) to CountryEO) Now add the RegionName field from the EO and a transient attribute (I named mine RegionNameLOV) Make the transient attribute updateable and base it on the expression RegionName (the description you wish to display) Add a list of values to RegionNameLOV and map BOTH key to parent fk (region id here) AND RegionName to your transient coulmn (RegionNameLOV).  Map the transient as an Input text with List of Values. Then just drag the lov item onto the page (RegionNameLOV)

ADF sort of generic screen for tables with the same structure

We have a couple (about a hundred) of tables with the same structure (Code, Description, Create Date, Update Date). So I wanted to do something simple so that I did not have to create all these screens 1) EO   I created the EO based on one of the tables I had that had the above columns. I then Added a transient attribute called table name to my EO based on a groovy expression. (the expression needs to change as I am reading web tier stuff from the model layer but I will fix this later) I then generated a java class for my EO. And added the following overriden method to my newly created java class. protected StringBuffer buildDMLStatement(int i, AttributeDefImpl[] attributeDefImpl,   AttributeDefImpl[] attributeDefImpl2, AttributeDefImpl[] attributeDefImpl3, boolean b) {   StringBuffer statement = super.buildDMLStatement(   i, attributeDefImpl, attributeDefImpl2, attributeDefImpl3, b); return new StringBuffer(StringUtils.replace(statement.to...