Tree selection (single selection model) but on 2 panels

hi..
here is my problem..
I have 2 trees each with single selection mode.
i add them to 2 scrollpanes and add these 2 scrollpanes to a split pane and divided them vertically.
When i select the tree node in the upper pane the corresponding node is displayed as the root of the tree in lower pane, so far so fine.
when i select the tree node in the lower pane the tree which was already selected in the upper pane is deselected. while i want that selection to remain..
help me to solve this..
thanx in advance..
K�vi

you can only have 1 focused component, but trees shouldn't lose selection just cuz they lose focus.... unless you have a custom cell renderer for the tree and you are using the wrong options to paint the cell selection with.

Similar Messages

Diffrence b/w select single & select upto one row

hi
wat is the diffrence b/w select single & select upto one row?
deepak

Hi,
Select single has to be used with a where condition that has all the key fields:
It will always return a unique record(If a match is found).
Select upto 1 rows would get your the first record if multiple matches are found.
and select up to has to be end with endselect statements.
According to SAP Performance course the SELECT UP TO 1 ROWS is faster than SELECT SINGLE because you are not using all the primary key fields.
select single is a construct designed to read database records with primary key. In the absence of the primary key, it might end up doing a sequential search, whereas the select up to 1 rows may assume that there is no primary key supplied and will try to find most suitable index.
The best way to find out is through sql trace or runtime analysis.
Use "select up to 1 rows" only if you are sure that all the records returned will have the same value for the field(s) you are interested in. If not, you will be reading only the first record which matches the criteria, but may be the second or the third record has the value you are looking for.
The System test result showed that the variant Single * takes less time than Up to 1 rows as there is an additional level for COUNT STOP KEY for SELECT ENDSELECT UP TO 1 ROWS.
The 'SELECT SINGLE' statement selects the first row in the database that it finds that fulfils the 'WHERE' clause If this results in multiple records then only the first one will be returned and therefore may not be unique.
Mainly: to read data from
The 'SELECT .... UP TO 1 ROWS' statement is subtly different. The database selects all of the relevant records that are defined by the WHERE clause, applies any aggregate, ordering or grouping functions to them and then returns the first record of the result set.
Mainly: to check if entries exist.
When you say SELECT SINGLE, it means that you are expecting only one row to be present in the database for the condition you're going to specify in the WHERE clause. so that means, you will have to specify the primary key in your WHERE clause. Otherwise you get a warning.
SELECT UP TO 1 ROWS is used in cases where you just want to make sure that there is at least one entry in the database table which satisfies your WHERE clause. Generally, it is meant to be used for existence-check.
You may not want to really use the values returned by the SELECT statement in this case (thought this may not necessarily be so).And in each case the database optimizer may choose a different strategy to retrieve the data.
Knowing when to use SELECT SINGLE or SELECT ... UP TO 1 ROWS
A lot of people use the SELECT SINGLE statement to check for the existence of a value in a database. Other people prefer to use the 'UP TO 1 ROWS' variant of the SELECT statement.
So what's the difference between using 'SELECT SINGLE' statement as against a 'SELECT .... UP TO 1 ROWS' statement ?
If you're considering the statements
SELECT SINGLE field INTO w_field FROM table.
and
SELECT field INTO w_field FROM table UP TO 1 ROWS. ENDSELECT.
then looking at the result, not much apart from the extra ENDSELECT statement. Look at the run time and memory usage and they may be worlds apart.
Why is this ?? The answer is simple.
The 'SELECT SINGLE' statement selects the first row in the database that it finds that fulfils the 'WHERE' clause If this results in multiple records then only the first one will be returned and therefore may not be unique.
The 'SELECT .... UP TO 1 ROWS' statement is subtly different. The database selects all of the relevant records that are defined by the WHERE clause, applies any aggregate, ordering or grouping functions to them and then returns the first record of the result set.
According to SAP Performance course the SELECT UP TO 1 ROWS is faster than SELECT SINGLE because you are not using all the primary key fields.
http://sap-img.com/abap/difference-between-select-single-and-select-upto-one-rows.htm
Check these links -
The specified item was not found.
diff between select single and up to one row
diff b/w SECELT SINGLE * AND SELECT UPTO ONE ROW
Regards,
Priyanka.

Difference between select single * & select upto 1 rows

difference between select single * & select upto 1 rows

Hi,
According to SAP Performance course the SELECT UP TO 1 ROWS is faster than SELECT SINGLE because you are not using all the primary key fields.
Select single is a construct designed to read database records with primary key. In the absence of the primary key, it might end up doing a sequential search, whereas the select up to 1 rows may assume that there is no primary key supplied and will try to find most suitable index.
The best way to find out is through sql trace or runtime analysis.
Use "select up to 1 rows" only if you are sure that all the records returned will have the same value for the field(s) you are interested in. If not, you will be reading only the first record which matches the criteria, but may be the second or the third record has the value you are looking for.
The System test result showed that the variant Single * takes less time than Up to 1 rows as there is an additional level for COUNT STOP KEY for SELECT ENDSELECT UP TO 1 ROWS.
The 'SELECT SINGLE' statement selects the first row in the database that it finds that fulfils the 'WHERE' clause If this results in multiple records then only the first one will be returned and therefore may not be unique.
Mainly: to read data from
The 'SELECT .... UP TO 1 ROWS' statement is subtly different. The database selects all of the relevant records that are defined by the WHERE clause, applies any aggregate, ordering or grouping functions to them and then returns the first record of the result set.
Mainly: to check if entries exist.
Select Single
You need to mention all the key fields of the table.
No END SELECT required.
More performance compared to upto 1 row.
Where as UP to 1 row.
YOu can use if you do not have all the primiary key fields available.
END SELECT requeired.
Since all keys are not passing, possiblities of have other rows which satisfies the condition.
Select Statement with EndSelect is a loop, which in a single run retrieves a single Record. This Record has to be stored in a Work Area and then appended into an Internal Table.
Select Statements without EndSelect is not a loop and it retrieves the whole Record set matching the Criteria in a single shot and has to be Stored in an Internal Table Directly.
The most important thing to remember about the SELECT SINGLE is
There are several things to remember:
1) It retrieves only one row
2) It does not need an ENDSELECT statement
3) THE FULL KEY OF THE TABLE MUST BE INCLUDED IN
THE WHERE CLAUSE OF THE SELECT STATEMENT
Regards

Select single & select upto n row .

Hi,
Can anyone tell me the actual difference between select single & select upto n rows . which has the good performance .
Can anyone send a sample code for that.

Hi
Difference Between Select Single and Select UpTo One Rows
According to SAP Performance course the SELECT UP TO 1 ROWS is faster than SELECT SINGLE because you are not using all the primary key fields.
select single is a construct designed to read database records with primary key. In the absence of the primary key, it might end up doing a sequential search, whereas the select up to 1 rows may assume that there is no primary key supplied and will try to find most suitable index.
The best way to find out is through sql trace or runtime analysis.
Use "select up to 1 rows" only if you are sure that all the records returned will have the same value for the field(s) you are interested in. If not, you will be reading only the first record which matches the criteria, but may be the second or the third record has the value you are looking for.
The System test result showed that the variant Single * takes less time than Up to 1 rows as there is an additional level for COUNT STOP KEY for SELECT ENDSELECT UP TO 1 ROWS.
The 'SELECT SINGLE' statement selects the first row in the database that it finds that fulfils the 'WHERE' clause If this results in multiple records then only the first one will be returned and therefore may not be unique.
Mainly: to read data from
The 'SELECT .... UP TO 1 ROWS' statement is subtly different. The database selects all of the relevant records that are defined by the WHERE clause, applies any aggregate, ordering or grouping functions to them and then returns the first record of the result set.
Mainly: to check if entries exist.
<b>Reward points for useful Answers</b>
Regards
Anji

Select single * & Select * upto one row

What is the difference between Select single * & Select * upto one row?Performance wise which is a better one?

Hi,
According to SAP Performance course the SELECT UP TO 1 ROWS is faster than SELECT SINGLE because you are not using all the primary key fields.
Select single is a construct designed to read database records with primary key. In the absence of the primary key, it might end up doing a sequential search, whereas the select up to 1 rows may assume that there is no primary key supplied and will try to find most suitable index.
The best way to find out is through sql trace or runtime analysis.
Use "select up to 1 rows" only if you are sure that all the records returned will have the same value for the field(s) you are interested in. If not, you will be reading only the first record which matches the criteria, but may be the second or the third record has the value you are looking for.
The System test result showed that the variant Single * takes less time than Up to 1 rows as there is an additional level for COUNT STOP KEY for SELECT ENDSELECT UP TO 1 ROWS.
The 'SELECT SINGLE' statement selects the first row in the database that it finds that fulfils the 'WHERE' clause If this results in multiple records then only the first one will be returned and therefore may not be unique.
Mainly: to read data from
The 'SELECT .... UP TO 1 ROWS' statement is subtly different. The database selects all of the relevant records that are defined by the WHERE clause, applies any aggregate, ordering or grouping functions to them and then returns the first record of the result set.
Mainly: to check if entries exist.
Select Single
You need to mention all the key fields of the table.
No END SELECT required.
More performance compared to upto 1 row.
Where as UP to 1 row.
YOu can use if you do not have all the primiary key fields available.
END SELECT requeired.
Since all keys are not passing, possiblities of have other rows which satisfies the condition.
Select Statement with EndSelect is a loop, which in a single run retrieves a single Record. This Record has to be stored in a Work Area and then appended into an Internal Table.
Select Statements without EndSelect is not a loop and it retrieves the whole Record set matching the Criteria in a single shot and has to be Stored in an Internal Table Directly.
The most important thing to remember about the SELECT SINGLE is
There are several things to remember:
1) It retrieves only one row
2) It does not need an ENDSELECT statement
3) THE FULL KEY OF THE TABLE MUST BE INCLUDED IN
THE WHERE CLAUSE OF THE SELECT STATEMENT
Regards

Difference between select single & select upto 1 row

Hi,
what is the Difference between select single & select upto 1 row?
Whose performance is better?
Regards,
Mayank

Hi
According to SAP Performance course the SELECT UP TO 1 ROWS is faster than SELECT SINGLE because you are not using all the primary key fields.
The 'SELECT SINGLE' statement selects the first row in the database that it finds that fulfils the 'WHERE' clause If this results in multiple records then only the first one will be returned and therefore may not be unique.
Mainly: to read data from
The 'SELECT .... UP TO 1 ROWS' statement is subtly different. The database selects all of the relevant records that are defined by the WHERE clause, applies any aggregate, ordering or grouping functions to them and then returns the first record of the result set.

SELECT SINGLE & SELECT UPTO 1 ROW

Dear All,
I want to optimise the Code performance.
I don't have full table key. So, what is better to use - SELECT SINGLE or SELECT UPTO 1 ROW?
Please ASAP.
Thanks in advance.
Prasad.

Hi ,
Difference Between Select Single and Select UpTo One Rows
According to SAP Performance course the SELECT UP TO 1 ROWS is faster than SELECT SINGLE because you are not using all the primary key fields.
select single is a construct designed to read database records with primary key. In the absence of the primary key, it might end up doing a sequential search, whereas the select up to 1 rows may assume that there is no primary key supplied and will try to find most suitable index.
The best way to find out is through sql trace or runtime analysis.
Use "select up to 1 rows" only if you are sure that all the records returned will have the same value for the field(s) you are interested in. If not, you will be reading only the first record which matches the criteria, but may be the second or the third record has the value you are looking for.
The System test result showed that the variant Single * takes less time than Up to 1 rows as there is an additional level for COUNT STOP KEY for SELECT ENDSELECT UP TO 1 ROWS.
The 'SELECT SINGLE' statement selects the first row in the database that it finds that fulfils the 'WHERE' clause If this results in multiple records then only the first one will be returned and therefore may not be unique.
Mainly: to read data from
The 'SELECT .... UP TO 1 ROWS' statement is subtly different. The database selects all of the relevant records that are defined by the WHERE clause, applies any aggregate, ordering or grouping functions to them and then returns the first record of the result set.
Mainly: to check if entries exist.
Regards
ANJI

Select Single & Select upto -- req when to use?

Hi Guys!
Can u pls tell me when to use select single * & when to use select upto 1 rows. with eg.
Thanks.

According to SAP Performance course the SELECT UP TO 1 ROWS is faster than SELECT SINGLE because you are not using all the primary key fields.
Select single is a construct designed to read database records with primary key. In the absence of the primary key, it might end up doing a sequential search, whereas the select up to 1 rows may assume that there is no primary key supplied and will try to find most suitable index.
The best way to find out is through sql trace or runtime analysis.
Use "select up to 1 rows" only if you are sure that all the records returned will have the same value for the field(s) you are interested in. If not, you will be reading only the first record which matches the criteria, but may be the second or the third record has the value you are looking for.
The System test result showed that the variant Single * takes less time than Up to 1 rows as there is an additional level for COUNT STOP KEY for SELECT ENDSELECT UP TO 1 ROWS.
The 'SELECT SINGLE' statement selects the first row in the database that it finds that fulfils the 'WHERE' clause If this results in multiple records then only the first one will be returned and therefore may not be unique.
Mainly: to read data from
The 'SELECT .... UP TO 1 ROWS' statement is subtly different. The database selects all of the relevant records that are defined by the WHERE clause, applies any aggregate, ordering or grouping functions to them and then returns the first record of the result set.
Mainly: to check if entries exist.
Select Single
You need to mention all the key fields of the table.
No END SELECT required.
More performance compared to upto 1 row.
Where as UP to 1 row.
YOu can use if you do not have all the primiary key fields available.
END SELECT requeired.
Since all keys are not passing, possiblities of have other rows which satisfies the condition.
Select Statement with EndSelect is a loop, which in a single run retrieves a single Record. This Record has to be stored in a Work Area and then appended into an Internal Table.
Select Statements without EndSelect is not a loop and it retrieves the whole Record set matching the Criteria in a single shot and has to be Stored in an Internal Table Directly.
The most important thing to remember about the SELECT SINGLE is
There are several things to remember:
1) It retrieves only one row
2) It does not need an ENDSELECT statement
3) THE FULL KEY OF THE TABLE MUST BE INCLUDED IN
THE WHERE CLAUSE OF THE SELECT STATEMENT
to say in simple
SELECT SINGLE:
1. Select single is based on PRIMARY KEY
2. It will take the first record directly without searching of all relevant records.(Though you have lot of records for given condition)
SELECT UPTO 1 ROW :
It will check all records for given condition and take the first record .
It means in select single no searching, where as other searching.
Therefore, select single more efficient than UPTO 1 ROW.

Difference bt select single & select up 1 record

What is the exact difference between select single and select up to 1 record

Hi
Difference Between Select Single and Select UpTo One Rows
According to SAP Performance course the SELECT UP TO 1 ROWS is faster than SELECT SINGLE because you are not using all the primary key fields.
select single is a construct designed to read database records with primary key. In the absence of the primary key, it might end up doing a sequential search, whereas the select up to 1 rows may assume that there is no primary key supplied and will try to find most suitable index.
The best way to find out is through sql trace or runtime analysis.
Use "select up to 1 rows" only if you are sure that all the records returned will have the same value for the field(s) you are interested in. If not, you will be reading only the first record which matches the criteria, but may be the second or the third record has the value you are looking for.
The System test result showed that the variant Single * takes less time than Up to 1 rows as there is an additional level for COUNT STOP KEY for SELECT ENDSELECT UP TO 1 ROWS.
The 'SELECT SINGLE' statement selects the first row in the database that it finds that fulfils the 'WHERE' clause If this results in multiple records then only the first one will be returned and therefore may not be unique.
Mainly: to read data from
The 'SELECT .... UP TO 1 ROWS' statement is subtly different. The database selects all of the relevant records that are defined by the WHERE clause, applies any aggregate, ordering or grouping functions to them and then returns the first record of the result set.
Mainly: to check if entries exist.
<b>Reward points for useful Answers</b>
Regards
Anji

Selecting A Female Model From Background - How To Help

Hello PSE users, thanks in advance for your help. Here's the image I have at hand: how do I make a selection around the model but excluding the object in her hand and everything else? I have quite a basic working knowledge of PSE and my skills are limited, unfortunately.
Thanks for your help!

The newest versions of PSE have the Magic Extractor tool which should do the trick. My version doesn't, so I used the Magnetic Lasso to select the model. Working on a duplicate of the Background layer I selected her and inverted the selection and deleted it, leaving just her on transparent background. To correct the blue color cast I use the Color Cast tool, clicking on the white of her teeth. Some portions of her outline had hard edges so I softened these with a combination of the Blur tool and a small soft Eraser (you can also soften the outline of the initial selection by feathering 1 or 2 px).
One more thing. There was a red streak down her face so I removed these by cloning adjacent area.
I added a light blue layer so you can see the result.

Visual Composer 7.0.1 (EHP1) - Value Help only shows "Single Selection"

I tried to add a value help to a field that allows multiple selections. However, when I used the wizard through "Add Value Help" drop-down menu, I can only see one proposed selection - "Single selection". However this SAP help document (http://help.sap.com/saphelp_nw70/helpdata/en/b5/036d391f074f769e00602634ee9960/content.htm) mentioned about the "Multiple selection" option. What I can do to make this selection available?
I am using VC 7.0.1 (EHP1). Thanks for any helps in advance.
Kelly

Hi
Are you using 'BI Query' as 'data Service'? & are you creating value help for variable? If Yes -
Create necessary variable as 'Multiple Single Options' in your BEx query & then create value help in VC. Then it will allow multiple options or interval values.
Regards
Sandeep

GetSelectedRowKeys() returns more than one on Single Selection Tree Table

Hi,
I found that this issue occurring after PS3 (I think.)
I have a tree table component, which allows single row selection. There is a listener on a column of the tree table as follows:
public void listenPackageUnit(ValueChangeEvent valueChangeEvent)
Object oldKey = getTreeComponent().getRowKey();
try
* Retrieve index of selected package unit
* NOTE: Subtract 1 to remove no selection value. This only
* needs to be done if attached LOV has No Selection option set.
if (valueChangeEvent.getNewValue() != null)
Row row = null;
String selectedPackageUnit = null;
int packageUnitIndex = (Integer) valueChangeEvent.getNewValue();
packageUnitIndex--;
* Due to the no selection item, we need to prevent search of regular
* iterator if index is < 0. In this case we know the user selected
* the no selection (blank) value.
if (packageUnitIndex >= 0)
* Using index, determine the value of the selected package unit
DCIteratorBinding packageUnitsIterator =
(DCIteratorBinding) PasUiADFUtil.resolveExpression("#{bindings.PackageUnitsIterator}");
Row newRow =
packageUnitsIterator.getRowAtRangeIndex(packageUnitIndex);
selectedPackageUnit = (String) newRow.getAttribute("LookupCode");
RowKeySet selection = this.getTreeComponent().getSelectedRowKeys();
if (selection != null && selection.getSize() > 0)
for (Object facesTreeRowKey: selection)
this.getTreeComponent().setRowKey(facesTreeRowKey);
JUCtrlHierNodeBinding rowData =
(JUCtrlHierNodeBinding) this.getTreeComponent().getRowData();
row = rowData.getRow();
setSelectedLabel((String) row.getAttribute("Label"));
setSelectedLabelType((String) row.getAttribute("LabelType"));
row.setAttribute("PackageUnit", selectedPackageUnit);
getTreeComponent().setRowKey(oldKey);
finally
getTreeComponent().setRowKey(oldKey);
The issue is that getSelectedRowKeys() returns more than one when the user selects a child row in the tree table.
It seems to be returning the total number counting from the top parent through the child.
(For example, if the child is the second generation, it returns 2, and if the third generation, it returns 3.)
This is causing the issue that the method tries to update the attribute of the parent row with a value for the child row. (And it fails, because the attribute is updateable only while new.)
I remember getSelectedRowKeys() always returned one, the selected child itself, when I coded this around October, 2010.
Is this a design change after PS3? Why does it return more than one though the tree table is for single selection?
How can I get around this issue?
It would be truly appreciated if we can get any quick help, since we are at final testing phase of our product.
Thank you,
Tomo

Hi Vinod,
I found the solution. Thank you very much for your suggestions. :)
Now my listenSelection (custom listener of the tree table) looks like below:
public void listenSelection(SelectionEvent selectionEvent)
Row currentRow;
PasUiADFUtil.invokeEL("#{bindings.TransactionLabelTopLevelVO1.collectionModel.makeCurrent}",
new Class[] { SelectionEvent.class },
new Object[] { selectionEvent });
Object oldKey = getTreeComponent().getRowKey();
try
if (this.getTreeComponent() != null)
RowKeySet rks = this.getTreeComponent().getSelectedRowKeys();
Iterator keys = rks.iterator();
while (keys.hasNext())
List key = (List) keys.next();
this.getTreeComponent().setRowKey(key);
JUCtrlHierNodeBinding node =
(JUCtrlHierNodeBinding) this.getTreeComponent().getRowData();
if (node != null)
currentRow = node.getRow();
if (currentRow != null)
this.setSelectedRow(currentRow);
setSelectedLabel((String) currentRow.getAttribute("Label"));
setSelectedLabelType((String) currentRow.getAttribute("LabelType"));
String shippedItemFlag =
(String) currentRow.getAttribute("ShippedItemFlagValue");
if (shippedItemFlag != null && shippedItemFlag.equals("1"))
setDisableAdd(true);
else
setDisableAdd(false);
finally
getTreeComponent().setRowKey(oldKey);
/* Refresh Action menu and buttons */
RequestContext.getCurrentInstance().addPartialTarget(this.getActionMenu());
RequestContext.getCurrentInstance().addPartialTarget(this.getToolbar());
And my tree table is like below:
<af:treeTable value="#{bindings.TransactionLabelTopLevelVO1.treeModel}"
var="node" rowSelection="single" id="tt1"
contentDelivery="immediate" fetchSize="25"
emptyText="#{bindings.TransactionLabelTopLevelVO1.viewable ? commonFoundationMsgBundle.NO_DATA_TO_DISPLAY : commonFoundationMsgBundle.ACCESS_DENIED}"
selectionListener="#{pageFlowScope.MaintainTransactionSerialAssociationBean.listenSelection}"
binding="#{pageFlowScope.MaintainTransactionSerialAssociationBean.treeComponent}"
summary="#{maintainAssociationUiBundle.CONTAINER_SERIAL_HIERARCHY}">

The listener is now always getting the currently selected row only.
Tomo

SSRS report - A single selection dropdown list converted to text box

Hello everyone,
We created a single selection dropdown parameter (City parameter) on a report. The data in this parameter is populated using MDX query. Also, it is filtered based on selection of another single selection dropdown list (Country parameter) of a report.
The problem is when there is no cities for the selected country the dropdown list is gets converted to free type text box and user can insert city data in it. Why SSRS is not keeping it as empty dropdown list with no data?
Any help would be much appreciated.
Thanks, Ankit Shah
Inkey Solutions, India.
Microsoft Certified Business Management Solutions Professionals
http://www.inkeysolutions.com/MicrosoftDynamicsCRM.html

Hello Charlie,
We developed a fresh report only with two parameters but still the dropdown control gets converted to text box in our case. We have two single selection parameters, Location and Customers. Based on selected Location the customer
dropdown gets populated.
Location Parameter Query
WITH MEMBER [Measures].[ParameterCaption] AS [Location].[Location Name].CURRENTMEMBER.MEMBER_CAPTION MEMBER [Measures].[ParameterValue] AS [Location].[Location Name].CURRENTMEMBER.UNIQUENAME MEMBER
[Measures].[ParameterLevel] AS [Location].[Location Name].CURRENTMEMBER.LEVEL.ORDINAL
SELECT {[Measures].[ParameterCaption], [Measures].[ParameterValue], [Measures].[ParameterLevel]} ON COLUMNS , [Location].[Location Name].ALLMEMBERS ON ROWS FROM [Model]
Customer Query
WITH MEMBER [Measures].[ParameterCaption] AS
[Customer].[Customer Name].CURRENTMEMBER.MEMBER_CAPTION
MEMBER [Measures].[ParameterValue] AS
[Customer].[Customer Name].CURRENTMEMBER.UNIQUENAME
MEMBER [Measures].[ParameterLevel] AS [Customer].[Customer Name].CURRENTMEMBER.LEVEL.ORDINAL
SELECT {[Measures].[ParameterCaption], [Measures].[ParameterValue], [Measures].[ParameterLevel],[Measures].[Amt]} ON COLUMNS,
nonempty([Customer].[Customer Name].ALLMEMBERS,[Measures].[Amt]) ON ROWS FROM ( SELECT ( STRTOSET(@LocationName, CONSTRAINED) ) ON COLUMNS FROM [Model])
Regarding parameter settings on General tab for both the above parameters we did not select any of the following values, all these checkboxes are empty:
Allow Blank Value ("") , Allow null value, Allow multiple values.
I think it has something related to [Measures].[Amt] that we used in customer parameter. We are now trying to take other two parameters where we would be not using the [Measures].[Amt] to filter the data. Will update you soon.
Thanks, Ankit Shah
Inkey Solutions, India.
Microsoft Certified Business Management Solutions Professionals
http://www.inkeysolutions.com/MicrosoftDynamicsCRM.html

LOV single selection list is not working in my JDeveloper 10.1.2.3

Hi!
I'm stumped with this. I'm also new to JDeveloper. I used the sample tutorial from the OTN website entitled "JSPDataBoundLists.jws" to learn how to create drop-down lists in JDeveloper.
My problem is I created a single selection list LOV from DepartmentListView Data Control and pasted it into an EmployeesView Input form. This is so I can just select the Department names to populate the DepartmentID field in Employees table. I setup the data binding in the UI Model of my jsp using the "List Binding Editor". I checked the UIModel file and it looks as follows:
<DCControl
id="DepartmentId2"
SubType="DCListSingleSel"
IterBinding="EmployeesViewIterator"
DTClass="oracle.adf.dt.objects.JUDTCtrlListLOV"
ApplyValidation="false"
isDynamic="false"
ListOperMode="0"
ListIter="DepartmentsListViewIterator" >
<AttrNames>
<Item Value="DepartmentId" />
</AttrNames>
<ListAttrNames>
<Item Value="DepartmentId" />
</ListAttrNames>
<ListDisplayAttrNames>
<Item Value="DepartmentName" />
</ListDisplayAttrNames>
</DCControl>
I run the jsp, selected a value from the drop-down list, do a submit and do a commit, but the DepartmentId from the DepartmentsListView was not stored in Employees. What is wierd here is that there is an exact same single selection list defined a row above mine which is working fine. How come that one is working and mine is not?

Eureka! I finally found the answer to my own question!
This simple problem of adding a drop-down list into a jsp page cost me 3 whole days (around 24 full working hours) to find the answer. Normally it only takes me a few minutes with the other web app languages I've learned. And I just stumbled into the answer just a few minutes ago (maybe all thanks should be given to God whom let me stumble into the answer since me and my wife have been praying for several weeks now ever since I started trying to learn Oracle JDeveloper. It is really very very difficult and time consuming to learn compared to other web app languages and tools).
Anyway, the reason why my LOV does not work in my jsps using JDeveloper 10.1.2.3 is because JDeveloper 10.1.2.3 seems to allow only one input-form-element for the same field of the input table!
For example, what happened to me was I had an input form created for the Employees table in the HR schema. I did this simply by drag-and-drop from the "Data Control Palette". This feature I like very much with JDeveloper. It is really easy and works instantly. And then, I drag-and-drop the departmentname field from the Departments table as a "single selection list" into the jsp and setup its bindings. So when I run the jsp, viola! The drop-down list does not populate the DepartmentId field of the Employees table. IT DOES NOT WORK! I've tried reinstalling both JDev and Oracle db and JDKs to no avail! I tried posting in this forum to no avail! I tried experimenting with newly created jsps to no avail! Then suddenly after repeatedly experimenting on this on different tutorials, guides and my own web app, it works! Why did it work? It was because I tried to add an LOV-single-selection-list on another sample tutorial with a READ-ONLY FORM on the jsp! Thus only the LOV is the input-form-element in the jsp for the table's field.
So why can't you find such a simple and basic fact anywhere in the web, the tutorials, guides or the forum? I do not know. Maybe only I am using such an old version of JDev? But what about the users who used it when it just got out a couple of years ago? Didn't they have the same problem? Anyway, it seems like the answer to a lot of my simple basic questions about JDeveloper is not documented, or is buried very deep beneath all the other words of all these documents. Hopefully JDeveloper's documentations would get a lot easier to use very very soon!

Single selection choice only returning 25 items

JDeveloper 11.1.1.3.0
I have a single selection choice component being populated by a view object. When I run the app only 25 objects are returned in the dropdown. I have modified the tuning settings on the view object and have successful limited the results to less than 25, but never greater than 25.
I have tested the view object in the AppModule and the expected number of results are returned
I have tried various combinations of "All Rows";"Only Up to row number";"In Batches of";"As Needed"; "All at Once" as tuning parameters and have yet to return greater than 25
I have searched this form and internet, seems like an easy fix.
Any thoughts?
--Scott
Edited by: user9215946 on May 11, 2012 3:23 PM

The iterator’ s RangeSize attribute defines the number of records ADFm requests from the ADF BC layer simultaneously.
By default the RangeSize attribute is automatically set to 25 records when the iterator is created.
In order to reduce the number of round-trips between the model and BC layers to one (optimum behavior) Oracle recommends setting the RangeSize value to the number of records to be displayed in the UI simultaneously for the view object.http://www.gebs.ro/blog/oracle/adf-view-object-performance-tuning-analysis/
A range size of -1 will retrieve all rows at once from ADF BC layer. If you have a lot of rows this might be a performance constraint

Tree selection (single selection model) but on 2 panels

Similar Messages

Maybe you are looking for