Monday Sep 23, 2013

Override adf-config.xml's row fetch limit

Let's say you have a hard limit on row fetch set to 300 set in your application's adf-config.xml. If there is a functional/technical need to fetch let's say 500 rows-



You can do so by specifying the MaxFetchSize to a positive number(optimistically determined) in either your ViewObject xml or if it is a View Accessor then you can do so under the View accessor definition in the corresponding ViewObject.xml-



MaxFetchSize="<your number>" 

Wednesday Aug 07, 2013

Hiding view criteria item for specific view instance in nested view crietria scenario

Parent ViewObject: Dept


Child ViewObject: Emp


VL: DeptToEmpVL



Dept object members:


---------------------------


 View Criteria: DeptVC


Emp object members:


---------------------------


 View Criteria: EmpVC



In the DeptVC, lets say you have a nested Emp VC included with exists clause.


 Drag and drop Dept view instance in a page, run the page. You will notice that the Add Fields dropdown contains all the attributes from emp view. What if you don't want some emp view attributes to be exposed here.



Edit the  DeptVC, add those specific criteria items to you nested VC, if you don't want to display those items neither in the query panel nor in the add fields drop down  as mentioned below-


<Properties>
                <CustomProperties>
                  <Property
                    Name="renderedMode"
                    Value="Never"/>
                </CustomProperties>
                <SchemaBasedProperties>
                  <DISPLAYHINT
                    Value="Hide"/>
                </SchemaBasedProperties>
              </Properties>




if you just want to hide it from the query panel but you want it to appear in add fields dropdown-


<CustomProperties>
                  <Property
                    Name="renderedMode"
                    Value="Never"/>
                </CustomProperties>


By default if you don't specify an criteria item in your nested VC, all the attributes will appear in the add fields dropdown but none will appear in the query panel.




Tuesday Jun 01, 2010

Sorting: TransientVO Vs Query/EO based VO

In ADF, you can do a sorting on VO rows by invoking setSortBy("VOAttrName") API, but the tricky part is that, this API actually appends a clause to VO query at runtime and the actual sorting is performed after doing VO.executeQuery(), this goes fine for Query/EO based VO. But, how about the transient VO, wherein the rows are populated programmatically..?

There is a way to it..:)

you can actually specify the query mode on your transient VO, so that the sorting happens on already populated VO rows.

Here are the steps to go about it..

//Populate your transient VO rows.
//VO.setSortBy("YourVOAttrName");
//VO.setQueryMode(ViewObject.QUERY_MODE_SCAN_VIEW_ROWS);
//VO.executeQuery();

So, here the executeQuery() is actually the trigger which calls for VO rows sorting.
QUERY_MODE_SCAN_VIEW_ROWS flag makes sure that the sorting is performed on the already populated VO cache.

About

Talk on ADF (Mail To: vijay.x.mohan@oracle.com)

Search

Categories
Archives
« February 2015
SunMonTueWedThuFriSat
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
       
       
Today