Set view criteria in ViewObject

Studio Edition Version 11.1.1.3.0
I like to set view criteria in my view object implementation, but not work. the vc=getViewCriteria(crit) return not null but the attribute are not found
public void setViewCriteriaAttr(String crit, String attr, Object o){
    ViewCriteria vc = getViewCriteria(crit);
        if (vc != null) {
          ViewCriteriaRow vcr = (ViewCriteriaRow)vc.first();
          while (vcr != null) {
            String criteria = (String)vcr.getAttribute(attr);
            if (criteria != null) {
              vcr.setAttribute(attr,o);
            vcr = (ViewCriteriaRow)vc.next();
}Thx for help
Thomas
Edited by: thietho on 10.01.2011 12:11

Hi,
works for me, so the problem seems to be the way you call the method. Do you apply the VC somwhere in your code?
Frank

Similar Messages

Set view criteria on af:query choice LOV field

i have an af:query. one of the fields is a choice. the LOV for the choice come from a VO. i need to set view criteria for the query for the LOV for the choice. that is, the query for the values of the choice requires view criteria.
moreover, that search criteria is only known by the view. because the hooks for the choice are set up entirely in the model, i don't see how it would ever be possible to use values from the view to define the query for the LOV for the choice.
any ideas?

Assuming that you can have a method at the AM level that sets the viewCriteria for your VO, you can drag this method to the page flow to be executed before you go into the query page - this will set the right condition for the list that needs to populate the LOV.
Then the query component can use that VO as an LOV like this:
http://blogs.oracle.com/shay/2009/12/adf_query_with_parameters_and_1.html

Programmtically Setting View Criteria in ADF Query Component

I have created two view criterias for a View Object and used ADF Query component for searching. User can select any one of the View Criteria from "saved search" in ADF Query component. but i want to set it programmatically based on some business rules. How i can do that?

No I don't want to set view criteria on search click. Actually I have ADF Query component on my page which is by default disabled. There are also some fields outside the query component on the value of which i enable ADF Query component and wants to set a particular ViewCriteria based on context. All ViewCriterias are defined and listed in "saved search" of ADF Query component but i don't want to allow user to select it but wants to application set it automatically based on context. For it i will be needed to set a particualar ViewCriteria for ADF Query component through code and then refresh ADF Query component to show newly set ViewCriteria. I know how to refresh query component or any other component through code but don't know how to set ViewCriteria on ADF Query component?

Is it even possible to dynamically apply view criteria in an ADF Web App?

This is one of those situations where something that should take an hour ends up taking days.
* I have a view.
* The view has Bind Variables associated with it.
* The view has View Criteria associated with it.
* Each of the View Criteria use different Bind Variables.
* I have a search criteria input page that receives from the user what will ultimately be used to set the bind variables.
* I have a search results page that uses the view to display a table.
* I have the code that dynamically sets view criteria and parameters. It is based on the following:
http://download.oracle.com/docs/cd/E15523_01/web.1111/b31974/bcadvvo.htm#BCGFHAGA
* This code works great, until the iterator associated with the table binding to the view is initialized. At that time, the view is reset to its defaults, and all of my code's doings are discarded. How do I know this? Because I have gone so far as to run my code that sets view criteria and binding variables dynamically in a phase event handler for the search results page in the render response phase. There is no other point at which to dynamically modify the view.
This is turning into a situation where it seems I will need 5 different views and 5 different pages in order to show a single set of query results. I cannot get dynamically applied view criteria to work in an ADF web app. Has anyone else done it? Can anyone relate to this? Are there any other suggestions before I conclude that it's not possible for this framework to handle this simple scenario?
Thanks

There must be a setting or something that I am still missing here. If I write code just like this and make sure it is executed, I still only see the results of my view executed without the view criteria applied using the default bind variable values that I supplied in the view object.
It's like the fact that I set the bind variables, the view criteria, and executed the view query programmatically is lost on the iterator -- it's like it never happened. What setting is used to ensure that the iterator uses the outcome of what I executed programmatically? There has to be a critical set or setting that I am missing.
Here is the iterator and search region definitions defined in the page def "executables" section:
<executables>
     <iterator Binds="CustomSearchView1" RangeSize="25"
              DataControl="AppModuleDataControl"
              id="CustomSearchView1Iterator"/>
    <searchRegion Binds="CustomSearchView1Iterator"
                  Customizer="oracle.jbo.uicli.binding.JUSearchBindingCustomizer"
                  id="CustomSearchView1Query"/>
    </executables>Here's the "tree" binding in the page def file:
<bindings>
   <tree IterBinding="CustomSearchView1Iterator" id="CustomSearchView1">
      <nodeDefinition DefName="Model.CustomSearchView" Name="CustomSearchView10">
        <AttrNames>
          <Item Value="CustomId"/>
          <Item Value="CustomProjectNumber"/>
          <Item Value="CustomName"/>
          <Item Value="CustomStatus"/>
          <Item Value="CustomStatusDate"/>
        </AttrNames>
      </nodeDefinition>
    </tree>
</bindings>In an effort to take page flow out of this mess, I had modified this to include the search criteria and search results on a single page. So, I now have a "Search" button. When the "Search" button is clicked, the action method does the following:
    public String searchActionListener ()
          // Get search criteria from select one choice and text input controls.
          AppModule appModule =
                ( AppModule ) Configuration.createRootApplicationModule (
                    "Model.AppModule",
                    "AppModuleLocal");
          appModule.customSearch( searchCriteria1,
                                               searchCriteria2,
                                               searchCriteria3 );
    }In my application module this translates to:
    public void customNoticeSearch ( String searchCriteria1, String searchCriteria2, String searchCriteria3)
       CustomSearchViewImpl searchViewImp =
           ( CustomSearchViewImpl ) this.getCustomSearchView1 ();
       searchViewImp.customExecuteQuery ( searchCriteria1, searchCriteria2, searchCriteria3);
    }Finally, in my custom view object implementation code:
    public void customExecuteQuery ( String searchCriteria1, String searchCriteria2, String searchCriteria3 )
        // Set-up the parameters that are part of the core query.
        this.setp_searchCriteria1( searchCriteria1);
        this.setp_searchCriteria2( searchCriteria2);
        if ( searchCriteria3 != null )
            ViewCriteriaManager vcm = this.getViewCriteriaManager();
            ViewCriteria vc = vcm.getViewCriteria ( "WithLastCriteria" );
            this.setp_searchCriteria3( new Number ( searchCriteria3 ) );
            this.applyViewCriteria( vc );
        System.out.println ("This is fun.");
        this.executeQuery();
    }This code executes, but the results table is empty, and I know that there are results, because I can execute use execute with params to execute the base query and get the correct results back.
Thanks for taking a look at this.

Applying view criteria dynamically

Hi,
its urgent...... please guide me....
in my application I want to execute the viewobject once using database than it should store in cache memory and after applying view criteria it should filter the data and give from the memory after clearing it it should return all the records from the cache memory no need to go database...
I have used the following code......
public void getViewdata()
               ApplicationModule am = Configuration.createRootApplicationModule("model.HRAppModule", "HRAppModuleLocal");
        ViewObject viewobject = am.findViewObject("employeesVo1");
        viewobject.executeQuery();
              System.out.println("no of records:\t" + viewobject.getRowCount());
        System.out.println("no of records:\t " + viewobject.getFetchedRowCount());
        System.out.println("no of records:\t" + viewobject.getEstimatedRowCount());
        System.out.println("Query Mode of viewobject:\t" + viewobject.getQueryMode());
        ViewCriteria Viewcriteria = null;
        Viewcriteria = viewobject.createViewCriteria();
        Viewcriteria.setCriteriaMode(Viewcriteria.CRITERIA_MODE_QUERY | Viewcriteria.CRITERIA_MODE_CACHE);
        System.out.println("Viewcriteria mode is:\t" + Viewcriteria.getCriteriaMode());
        viewobject.setQueryMode(viewobject.QUERY_MODE_SCAN_VIEW_ROWS);
        System.out.println("Query Mode of viewobject:\t" + viewobject.getQueryMode());
        Viewcriteria.setConjunction(Viewcriteria.VC_CONJ_AND);
        ViewCriteriaRow Viewcriteriarow = Viewcriteria.createViewCriteriaRow();
        ViewCriteriaRow Viewcriteriarow1 = Viewcriteria.createViewCriteriaRow();
        Viewcriteriarow.setAttribute("ManagerId", this.getMgr());
        Viewcriteriarow.setConjunction(Viewcriteriarow.VC_CONJ_AND);
        Viewcriteriarow1.setAttribute("Salary", this.getSal());
        Viewcriteriarow1.setConjunction(Viewcriteriarow.VC_CONJ_AND);
        Viewcriteria.add(Viewcriteriarow);
        Viewcriteria.add(Viewcriteriarow1);
        if (Viewcriteria.hasData())         {
            System.out.println("Query Mode of viewobject:\t" + viewobject.getQueryMode());
            viewobject.applyViewCriteria(Viewcriteria);
            viewobject.executeQuery();
            System.out.println("no of records after apply view criteria:\t" + viewobject.getRowCount());
            System.out.println("no of records after apply view criteria:\t" + viewobject.getFetchedRowCount());
            System.out.println("no of records after apply view criteria:\t" + viewobject.getEstimatedRowCount());
            System.out.println(" view criteria where clause:\t" + viewobject.getViewCriteria());
                       System.out.println("Viewcriteria mode is:\t" + Viewcriteria.getCriteriaMode());
            System.out.println("Query Mode of viewobject:\t" + viewobject.getQueryMode());
            System.out.println("Query :\t" + viewobject.getQuery());
        else
                      Viewcriteria.removeAllElements();
            viewobject.applyViewCriteria(Viewcriteria);
            System.out.println("Viewcriteria mode is:\t" + Viewcriteria.getCriteriaMode());
             System.out.println(" view criteria where clause:\t" + viewobject.getViewCriteria());
                       System.out.println("Query :\t" + viewobject.getQuery());
            viewobject.executeQuery();
            System.out.println("no of records after apply view criteria:\t" + viewobject.getRowCount());
            System.out.println("no of records after apply new view criteria:\t" + viewobject.getFetchedRowCount());
            System.out.println("no of records after applying new view criteria:\t" + viewobject.getEstimatedRowCount());
            System.out.println("Viewcriteria mode is:\t" + Viewcriteria.getCriteriaMode());
            System.out.println("Query Mode of viewobject:\t" + viewobject.getQueryMode());
        }Edited by: user13385388 on Jan 21, 2011 6:59 AM

Hi,
I'm not able to get that so I have put all the things u go through it tell me the solution please its urgent...... please guide me....
in my application I want to execute the viewobject once using database than it should store in cache memory and after applying view criteria it should filter the data and give from the memory after clearing it it should return all the records from the cache memory no need to go database...
I have used the following code......
backing bean code
public class Beanclass
    private String deptid;
    private String mgrid;
    private String sal;
    public void setDeptid(String deptid)
        this.deptid = deptid;
    public String getDeptid()
        return deptid;
    public void setSal(String sal)
        this.sal = sal;
    public String getSal()
        return sal;
    public String ROView_action()
        // Add event code here...
        FacesContext facesContext = FacesContext.getCurrentInstance();
        Application app = facesContext.getApplication();
        ExpressionFactory elFactory = app.getExpressionFactory();
        ELContext elContext = facesContext.getELContext();
        ValueExpression valueExp = elFactory.createValueExpression(elContext, "#{bindings}", Object.class);
        BindingContainer bindings = (BindingContainer) valueExp.getValue(elContext);
        DCIteratorBinding iter = (DCIteratorBinding) bindings.get("EmPdetails1Iterator"); //("employeesVo1Iterator");
        ViewObject viewobject = iter.getViewObject();
        System.out.println("no of records without applying view criteria value:\t" + viewobject.getRowCount());
        System.out.println("no of records without applying view criteria value:\t " + viewobject.getFetchedRowCount());
        System.out.println("no of records without applying view criteria value:\t" + viewobject.getEstimatedRowCount());
        System.out.println("Query Mode of viewobject before applying view criteria:\t" + viewobject.getQueryMode());
        ViewCriteria Viewcriteria = null;
        Viewcriteria = viewobject.createViewCriteria();
        Viewcriteria.setCriteriaMode(Viewcriteria.CRITERIA_MODE_CACHE);
        //Viewcriteria.setCriteriaMode(Viewcriteria.CRITERIA_MODE_QUERY | Viewcriteria.CRITERIA_MODE_CACHE);
        System.out.println("Viewcriteria mode is:\t" + Viewcriteria.getCriteriaMode());
        viewobject.setQueryMode(viewobject.QUERY_MODE_SCAN_VIEW_ROWS);
        System.out.println("Query Mode of viewobject:\t" + viewobject.getQueryMode());
        Viewcriteria.setConjunction(Viewcriteria.VC_CONJ_AND);
        ViewCriteriaRow Viewcriteriarow = Viewcriteria.createViewCriteriaRow();
        ViewCriteriaRow Viewcriteriarow1 = Viewcriteria.createViewCriteriaRow();
        ViewCriteriaRow Viewcriteriarow2 = Viewcriteria.createViewCriteriaRow();
        Viewcriteriarow.setAttribute("DepartmentId", this.getDeptid());
        Viewcriteriarow.setConjunction(Viewcriteriarow.VC_CONJ_AND);
        Viewcriteriarow1.setAttribute("ManagerId", this.getMgrid());
        Viewcriteriarow1.setConjunction(Viewcriteriarow.VC_CONJ_AND);
        Viewcriteriarow2.setAttribute("Salary", this.getSal());
        Viewcriteriarow2.setConjunction(Viewcriteriarow.VC_CONJ_AND);
        Viewcriteria.add(Viewcriteriarow);
        Viewcriteria.add(Viewcriteriarow1);
        Viewcriteria.add(Viewcriteriarow2);
        viewobject.applyViewCriteria(Viewcriteria);
        viewobject.executeQuery();
        System.out.println("no of records after applying view criteria value:\t" + viewobject.getRowCount());
        System.out.println("no of records after applying view criteria value:\t" + viewobject.getFetchedRowCount());
        System.out.println("no of records after applying view criteria value:\t" + viewobject.getEstimatedRowCount());
        System.out.println("Viewcriteria mode is:\t" + Viewcriteria.getCriteriaMode());
        System.out.println("Query Mode of viewobject:\t" + viewobject.getQueryMode());
        Viewcriteria.removeAllElements();
        viewobject.applyViewCriteria(Viewcriteria);
        // viewobject.setQueryMode(viewobject.QUERY_MODE_SCAN_DATABASE_TABLES);
        viewobject.executeQuery();
        System.out.println("no of records after removing view criteria:\t" + viewobject.getRowCount());
        System.out.println("no of records after removing view criteria:\t" + viewobject.getFetchedRowCount());
        System.out.println("no of records after removing view criteria:\t" + viewobject.getEstimatedRowCount());
        System.out.println("Viewcriteria mode is:\t" + Viewcriteria.getCriteriaMode());
        System.out.println("Query Mode of viewobject:\t" + viewobject.getQueryMode());
        return null;
}Jspx code
<?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/templates/threeColumnTemplate.jspx"
                         id="pt1">
          <f:facet name="center">
            <af:panelGroupLayout id="pgl2" layout="vertical"
                                 inlineStyle="width:1327px;">
              <af:table value="#{bindings.EmPdetails1.collectionModel}"
                        var="row" rows="#{bindings.EmPdetails1.rangeSize}"
                        emptyText="#{bindings.EmPdetails1.viewable ? 'No data to display.' : 'Access Denied.'}"
                        fetchSize="#{bindings.EmPdetails1.rangeSize}"
                        rowBandingInterval="0"
                        selectedRowKeys="#{bindings.EmPdetails1.collectionModel.selectedRow}"
                        selectionListener="#{bindings.EmPdetails1.collectionModel.makeCurrent}"
                        rowSelection="single" id="t1" partialTriggers="::cb1"
                        width="1290">
                <af:column sortProperty="DepartmentId" sortable="true"
                           headerText="#{bindings.EmPdetails1.hints.DepartmentId.label}"
                           id="c5">
                  <af:outputText value="#{row.DepartmentId}" id="ot11">
                    <af:convertNumber groupingUsed="false"
                                      pattern="#{bindings.EmPdetails1.hints.DepartmentId.format}"/>
                  </af:outputText>
                </af:column>
                <af:column sortProperty="DepartmentName" sortable="true"
                           headerText="#{bindings.EmPdetails1.hints.DepartmentName.label}"
                           id="c10">
                  <af:outputText value="#{row.DepartmentName}" id="ot3"/>
                </af:column>
                <af:column sortProperty="EmployeeId" sortable="true"
                           headerText="#{bindings.EmPdetails1.hints.EmployeeId.label}"
                           id="c1">
                  <af:outputText value="#{row.EmployeeId}" id="ot9">
                    <af:convertNumber groupingUsed="false"
                                      pattern="#{bindings.EmPdetails1.hints.EmployeeId.format}"/>
                  </af:outputText>
                </af:column>
                <af:column sortProperty="FirstName" sortable="true"
                           headerText="#{bindings.EmPdetails1.hints.FirstName.label}"
                           id="c9">
                  <af:outputText value="#{row.FirstName}" id="ot2"/>
                </af:column>
                <af:column sortProperty="LastName" sortable="true"
                           headerText="#{bindings.EmPdetails1.hints.LastName.label}"
                           id="c3">
                  <af:outputText value="#{row.LastName}" id="ot12"/>
                </af:column>
                <af:column sortProperty="Email" sortable="true"
                           headerText="#{bindings.EmPdetails1.hints.Email.label}"
                           id="c11">
                  <af:outputText value="#{row.Email}" id="ot10"/>
                </af:column>
                <af:column sortProperty="PhoneNumber" sortable="true"
                           headerText="#{bindings.EmPdetails1.hints.PhoneNumber.label}"
                           id="c6">
                  <af:outputText value="#{row.PhoneNumber}" id="ot7"/>
                </af:column>
                <af:column sortProperty="HireDate" sortable="true"
                           headerText="#{bindings.EmPdetails1.hints.HireDate.label}"
                           id="c7">
                  <af:outputText value="#{row.HireDate}" id="ot1">
                    <af:convertDateTime pattern="#{bindings.EmPdetails1.hints.HireDate.format}"/>
                  </af:outputText>
                </af:column>
                <af:column sortProperty="JobId" sortable="true"
                           headerText="#{bindings.EmPdetails1.hints.JobId.label}"
                           id="c4">
                  <af:outputText value="#{row.JobId}" id="ot5"/>
                </af:column>
                <af:column sortProperty="Salary" sortable="true"
                           headerText="#{bindings.EmPdetails1.hints.Salary.label}"
                           id="c12">
                  <af:outputText value="#{row.Salary}" id="ot8">
                    <af:convertNumber groupingUsed="false"
                                      pattern="#{bindings.EmPdetails1.hints.Salary.format}"/>
                  </af:outputText>
                </af:column>
                <af:column sortProperty="CommissionPct" sortable="true"
                           headerText="#{bindings.EmPdetails1.hints.CommissionPct.label}"
                           id="c2">
                  <af:outputText value="#{row.CommissionPct}" id="ot6">
                    <af:convertNumber groupingUsed="false"
                                      pattern="#{bindings.EmPdetails1.hints.CommissionPct.format}"/>
                  </af:outputText>
                </af:column>
                <af:column sortProperty="ManagerId" sortable="true"
                           headerText="#{bindings.EmPdetails1.hints.ManagerId.label}"
                           id="c8">
                  <af:outputText value="#{row.ManagerId}" id="ot4">
                    <af:convertNumber groupingUsed="false"
                                      pattern="#{bindings.EmPdetails1.hints.ManagerId.format}"/>
                  </af:outputText>
                </af:column>
              </af:table>
            </af:panelGroupLayout>
          </f:facet>
          <f:facet name="header"/>
          <f:facet name="start">
            <af:panelGroupLayout id="pgl1" layout="vertical">
              <af:inputText label="Department Id" id="it1"
                            value="#{Viewcriteriabackingbean.deptid}"/>
              <af:inputText label="Salary" id="it2"
                            value="#{Viewcriteriabackingbean.sal}"/>
              <af:commandButton text="ApplyviewcriteriaUsingIteratorBindingforROView" id="cb1"
                                partialTriggers="t1"
                                action="#{Viewcriteriabackingbean.ROView_action}"/>
            </af:panelGroupLayout>
          </f:facet>
          <f:facet name="branding"/>
          <f:facet name="copyright"/>
          <f:facet name="status"/>
          <f:attribute name="startColumnSize" value="200"/>
        </af:pageTemplate>
      </af:form>
    </af:document>
</f:view>

</jsp:root>output:
its returning the filtered records based on deptid and sal after removing view criteria its not returning the all the records its returns filtered records only.
Edited by: user13385388 on Jan 25, 2011 1:58 AM

Programatically set where clause or view criteria not working in managed bean

I get a view using finditerator then then apply setwhere or view criteria but it does not filter the original rows. code is as follows
DCIteratorBinding dcIter3 =
ADFUtils.findIterator("PlanColorsIterator");
ViewObject cvo = dcIter3.getViewObject();
cvo.setNamedWhereClauseParam("Plno","4000"); // not working
   /*   // not working
cvo.applyViewCriteria(cvo.getViewCriteriaManager().getViewCriteria("PlanColorsCriteria"));
cvo.ensureVariableManager().setVariableValue("Plno", "4000");
cvo.executeQuery();
/* not working
cvo.setWhereClause("plan_no = :ThePlanType");
cvo.defineNamedWhereClauseParam("ThePlanType", null, null);
cvo.setNamedWhereClauseParam("ThePlanType", "4000");
cvo.executeQuery();

thanks for reply.
Jdeveloper version is 11.1.1.4.0.
Actually the vo on which I am trying to set set where is used as source to act as cursor to get values from filtered rows using set where and copy the this cursor values to another target vo. I am not showing these source values just getting values.
DCIteratorBinding dcIter2 =
ADFUtils.findIterator("PlotDtl2Iterator");
ViewObject dvo = dcIter2.getViewObject();
// colors to copy
DCIteratorBinding dcIter3 =
ADFUtils.findIterator("PlanColorsIterator");
ViewObject cvo = dcIter3.getViewObject();
cvo.setNamedWhereClauseParam("Plno","4000");
cvo.applyViewCriteria(cvo.getViewCriteriaManager().getViewCriteria("PlanColorsCriteria"));
cvo.ensureVariableManager().setVariableValue("Plno", "4000");
cvo.executeQuery();
cvo.setWhereClause("plan_no = :ThePlanType");
cvo.defineNamedWhereClauseParam("ThePlanType", null, null);
cvo.setNamedWhereClauseParam("ThePlanType", "4000");
cvo.executeQuery();
int totalCount=cvo.getRowCount();
cvo.setRangeSize(totalCount);
Row[] rArray=cvo.getAllRowsInRange();
for (Row r:rArray){
NameValuePairs nvp = new NameValuePairs();
nvp.setAttribute("Description",r.getAttribute("Description"));
nvp.setAttribute("PlanNo",r.getAttribute("PlanNo"));
nvp.setAttribute("MainAcc",r.getAttribute("MainAcc"));
nvp.setAttribute("Plqty",r.getAttribute("Qty"));
nvp.setAttribute("Cdkid",r.getAttribute("CdkId"));
nvp.setAttribute("FabricCode",r.getAttribute("FabricCode"));
nvp.setAttribute("DyeWash",r.getAttribute("DyeWash"));
// nvp.setAttribute("Description","test");
Row drow = dvo.createAndInitRow(nvp);
dvo.insertRow(drow);

How to set the default value of a LOV that is found in a view criteria

HI,
I need to set the default value of an LOV that is found in a view criteria. I tried to set a groovy expression but unfortunately it wasn't read. i also tried to bind the LOV to a bind variable and set the value of the bind variable in the constructor of my backing bean but unfortunately the default value appeared the second time i entered the screen and not on page load.
Can anyone advise where can i set the default value,
Thanks

if you want some default value in LOV. you go to edit list of value wizard-> UI hint->include no selection Item checkbox -checked.use labeled item first of list- and beside that put the label. but when you try to get value, it will show null.but you can manipulate in ur java , if it default value

How to apply common View criteria for all LOV View programatically?

Hi,
In my application I use nearly 100 VOs, which will be mapped as LOV to some base VOs. These VOs are not only for LOV but also will be used directly in screen as read-only table. All these VOs contains EFF_BGN_DTand EFF_END_DT. Requirement is to display only the active records in VO.
We don't want to crete view criteria at design time for each and every VO. Instead we want to have a base ViewObjectImpl class, create at runtime and add this common criteria with the existing view criterias (If any given, which are actually required for the developer for screen specific functionality).
NOTE: As all of our VOs are custom java data source implemented and none of them have queries, we cannot use whereclause API but only ViewCriteria.
We want to create a view criteria, that somewhat looks like the below condition.
           (     (TO_CHAR( EffBgnDt, 'yyyy-mm-dd') <= '2010-02-01' )
             AND (TO_CHAR( EffEndDt, 'yyyy-mm-dd') >= '2010-02-01' )
             OR
           (     (TO_CHAR( EffBgnDt, 'yyyy-mm-dd') <= '2010-02-01' )
             AND (EffEndDt IS NULL )
           )Question:
1. Which is the best place in ViewObject class, where I will be able to create common view criteria, include it with existing criterias.
Thanks in Advance.
Raghu

No it is not working. I've tested. When i test your implementation in my sample using AM tester, it is not at all going inside getCriteriaItemClause(ViewCriteriaItem pViewCriteriaItem). For example when i say, AM.findViewObject(String ViewObjectName), followed by getEstimatedRowCount(), it should apply common filter criteria and give me the result.
Given below required scenario:
Department table:
ID     DEPT_NAME     START_DATE     END_DATE
1     Hr          1-Jan-2010
2     Purchasing     1-Jan-2010     31-Dec-2010
3     Shipping             1-Jan-2010     31-Dec-2055
4     Sales          1-Jan-2010
Common criteria to be applied (Programatically) : :bind_current_date between StartDate and EndDate or :bind_current_date >= StartDate and EndDate is null
VO specific view criteria (may vary VO to VO): DeptName not equal to 'Sales'
Expected Result:
Case 1:
         a. DeptView = AM.findViewObject("DepartmentVO")
         b. DeptView.getEstimatedRowCount()
          It should give me 3 records (Hr, Shipping, Sales)
Case 2:
         a. DeptView = AM.findViewObject("DepartmentVO")
         b. Create View Criteria 'NotSalesDeptVC', which should not list out Sales department.
         c. Apply NotSalesDeptVC using RowSet rowSet = (RowSet) this.findByViewCriteria(NotSalesDeptVC, -1, ViewObject.QUERY_MODE_SCAN_VIEW_ROWS)
         d. rowSet.getEstimatedRowCount()
          It is in-memory filtering, will not disturb the default rowset, should give me 2 records (Hr, Shipping)
Case 3:
         a. DeptView = AM.findViewObject("DepartmentVO")
         b. Apply 'NotSalesDeptVC' to the default row set, followed by executeQuery
         c. DeptView.getEstimatedRowCount()
          It should give me 2 records. (Hr, Shipping)
Case 4:
         a. DeptView = AM.findViewObject("DepartmentVO")
         b. Unapply the applied 'NotSalesDeptVC', followed by executeQuery
         c. DeptView.getEstimatedRowcount()
          It should give me 3 records (Hr, Shipping, Sales)Essence is at any point of time, User should always work with active records. He no need to write extra logic to retrieve only the active records but the base Viewobject impl should have. Note, All of my view objects are custom java data source implemented and not query based. Similarly it does not meant that all of my VOs will be having some business specific View criteria. Some VOs may have. Some VOs may not have. However basic active records criteria is applicable for all VOs

Apply View criteria at runtime to child View object

Hi,
I am facing issues while trying to assign View Criteria to child VO that is part of View hierarchy at runtime.
AM Model:
Parent VO ->
Child VO1
-> Child VO2
View Link between :
Parent VO -> Child VO1
Child VO1 -> Child VO2
I have to apply View criteria at runtime at Child VO1 & Child VO2, i tried setApplyViewCriteriaName from AMImpl for these VO but that doesnt work.
It works for Parent VO, So I concluded Apply VC doesnt work directly for Tree structure.
I then override executeQueryforCollection in the VO however i am never able to get the handle for the VO that is getting executed :
Here's what is happening when i fetch my VO tree from AM :
- Parent VO , Child VO are getting instantiated
- Parent VO executeQueryforCollection called
- ** After this a new instance of Child VO is getting instantiated and i dont have any control of setting the VC based on some custom property
as all get defaulted at this point.
Please suggest what can be done in this case.
PS : i can not hardcode the VC condition at View Link.
- Sam

I was able to set the VC condotinally based on property set at Parent level using following code in executeQueryForCollection :
ApplicationModule am= this.getApplicationModule();
ViewObject vo = am2.findViewObject("ParentView1");
prop = (String)vo.getProperty("Parent_prop");
if(propVo_prop.equals("Y"))
this.setApplyViewCriteriaName("VC");
super.executeQueryForCollection(object, object2, i);
is this the right way ? Any performance bottleneck ? This service can be called for 1000 Id's .
Please suggest if there is some better way.
Thanks
-Sam

Including additional where clause conditions to view criteria dynamically

Hi,
We have a set of view objects that serves as LOV for various other view objects. All such LOV view objects have three specific attributes, two date attributes namely EffectiveStartDate, EffectiveEndDate and a String attribute namely UserSwitch based on which the LOV list needs to be filtered.
All the view objects are having one or more view criterias with specific where clause conditions.
Apart from those view criteria conditions, invariantly, we need the following conditions also
:bindEffDate between EffectiveStartDate and EffectiveEndDate and UserSwitch = :bindUserSwitch.
We wish not to include the above condition in each and every view criteria of each and every view object (Since we have around 800 view objects and a minimum of 2 view criterias per view object). Instead, we created a dummy view object (BaseViewObject) with two bind variables :bindEffDate and :bindUserSwitch and all the LOV view objects were made to extend this BaseViewObject.
Therefore, whenever a view object atribute is attached with LOV using the above said LOV View Objects, the bind variables of the baseViewObject as well as the view object specific bind variables are available in the view accessors tab of the view object wizard where we can supply values to those bind variables.
Now, we need to construct the view criteria filter clause. To achieve this, we created a class, CustomCriteriaAdapter.java extending oracle.jbo.server.CriteriaAdapterImpl. In the getCriteriaClause() method, we included the follwoing code:
public String getCriteriaClause(ViewCriteria pViewCriteria)
ViewObject vo = pViewCriteria.getViewObject();
String userSelectSwitch = (String) vo.ensureVariableManager().getVariableValue("bindUserSwitch");
String effBgnDt = vo.getAttributeDef(vo.getAttributeIndexOf("EffectiveStartDate")).getName();
String effEndDt = vo.getAttributeDef(vo.getAttributeIndexOf("EffectiveEndDate")).getName();
String customCriteria = " ( :bindEffDate >= " + effBgnDt + " ) AND ( :bindEffDate <= " + effEndDt + " OR " + effEndDt + " IS NULL ) ";
StringBuffer completeCriteria = new StringBuffer();
String criteriaClause = super.getCriteriaClause(pViewCriteria);
if (criteriaClause != null && !criteriaClause.isEmpty())
completeCriteria.append(criteriaClause + " AND ");
completeCriteria.append(customCriteria);
if (userSelectSwitch != null && "Y".equals(userSelectSwitch))
String userSelectSw = vo.getAttributeDef(vo.getAttributeIndexOf("UserSwitch")).getName();
completeCriteria.append(" AND (" + userSelectSw + "='Y' ) ");
return completeCriteria.toString();
Issues:
The LOV list is not filtering the records based on the constructed conditions. Instead it is listing either all of the records considering only the view criteria conditions applied at design time irrespective of the userswitch and effectivedate conditions or the list is empty.
Here, my questions are,
1. Am I in the correct approach? If not, guide me in a more proper approach to achieve the same requirement.
2. If the way I am trying is correct, where things are going wrong and why the dynamic condition is not getting effected?
Kindly help in sorting out the issue.
Thanks in advance.

Hi Jobinesh,
Thanks for your response and yes, we have done exactly as what you have mentioned. As explained earlier, a baseViewObject along with its Impl class has been created and it will be extended by all the viewobjects meant for serving LOV. Therefore, the superClass for any such LOV viewObject is the baseViewObjectImpl class. In that baseViewObjectImpl(), we have over-rided the criteriaAdapter() method and returned an instance of our customCriteriaAdapter() class.
Below is the code we are using in the baseViewObjectImpl():
package model.base.vo;
import oracle.jbo.CriteriaAdapter;
import oracle.jbo.server.ViewObjectImpl;
public class BaseViewObjectImpl
extends ViewObjectImpl
* This is the default constructor (do not remove).
public BaseViewObjectImpl()
* Over-rided method of ViewObjectImpl class of the framework.
* Calls the customized criteria adapter so that the default where clauses are added to the view criteria.
* @return CriteriaAdapter.
@Override
public CriteriaAdapter getCriteriaAdapter()
return new CustomCriteriaAdapter();
I'll create a sample in HR schema and share with you shortly.
Thanks and regards.

View Criteria and Transient fields

Hello, I was wondering, is it possible to have View Criteria set on a Transient field? I have created a Transient field named "Field1". I then go to the Query tab in my ViewObject and select the option "Create new view criteria". Here I select the option "Add Item" and from Attribute list I select my field "Field1". However what I notice is that the "View Object Where Clause" does not get updated when the attribute I select is a transient field - when it is a normal field (i.e. from an Entity) it does get updated. This means that I am unable to create view criteria for transient fields. Is there a way how I can manage to do this?

Transient attributes are not based on database columns. This means that WHERE-clause on transient attributes is a non-sense. It makes sense to add conditions on transient attributes only if the view criteria will be executed as a filter in memory (see the "Query Execution Mode" property in the "Create View Criteria" dialog).

Null check for a bind variable in view criteria

Hi, Greetings.
I am using Jdeveloper 11.1.2.0.
I have a view object, LocationsView, for locations table of the XE database.
I want to apply a condition, ((:bind_var is null) or (:bind_var is not null and location_id = :bind_var), in this LocationsView.
That is, I want to apply the condition only if the bind variable value is not null.
How can I construct this condition using a declarative view criteria?
Any help and hints on this regard is greatly appreciated.
Regards,
Guru K

Hi,
Thanks for the update and it is working perfectly fine.
Now, how can I set the "ignore null values" option as checked if I am constructing the criteria programmatically using view criteria row and view criteria item at runtime.
Thanks and regards,
Guru K

View Criteria issue on ADF Tree

Hi,
JDev 11.1.1.5.0
I am facing an issue while displaying ADF tree. I've created ParentVO & ChildVO from a single table with view criteria to filter the nodes.And then created two View links ParentToChild & ChildToChild.
Added VOs & corresponding ViewLinks to ApplicationModule. When I tried to run application module, getting the results as per expectation (applying view criteria at each level).
Now i've dragged the parent vo from data control on to jspx page. when I run the jspx page, it's displaying the tree structure.
Issue is only view criteria is applying for top level nodes(parent VO) but not sub levels. If there is some issue with creation of View criteria then it should give same problem while executing AM. But while running AM, getting the expected results.
It would be great if you provide any clue on this issue
Thanks,
Samba

Thanks for your response.
But my usecase is different. I need to filter the sublevels of the tree.
Following is the sample
Level1
     Level1.1
     Level1.2
     Level1.3
Level2
     Level2.1
     Level2.2
     Level2.3
     Level2.4
Level3
     Level3.1
     Level3.2
     Level3.3
If I gave View Criteria as contains '2' then, Need to filter the nodes contains character 2. Able to filter first level nodes according VC. But VC is not applying for sub levels. Is there any way to set the VC in my case?

How can I use a single query panel with two view criteria?

Hi all,
I have a requirement to allow users to change the "display mode" on a search results tree table for an advanced search page. What this will do is change the structure of how the data is laid out. In one case the tree table is 3 levels deep, in the other case it's only 2 with different data being at the root node.
What I've done so far:
1) I exposed the data relationship for these two ways of viewing the data in the application module's data model.
2) I created a view criteria in the two view objects that are at the root of the relationships, where (for simplicity sake) I'm only comparing a single field.
This is in one view object:
<ViewCriteria
    Name="PartsVOCriteria"
    ViewObjectName="gov.nasa.jpl.ocio.qars.model.views.PartsVO"
    Conjunction="AND">
    <Properties>... </Properties>
    <ViewCriteriaRow
      Name="vcrow23"
      UpperColumns="1">
      <ViewCriteriaItem
        Name="PartDiscrepantItemsWithIRVO"
        ViewAttribute="PartDiscrepantItemsWithIRVO"
        Operator="EXISTS"
        Conjunction="AND"
        IsNestedCriteria="true"
        Required="Optional">
        <ViewCriteria
          Name="PartDiscrepantItemsWithIRVONestedCriteria"
          ViewObjectName="gov.nasa.jpl.ocio.qars.model.views.PartDiscrepantItemsWithIRVO"
          Conjunction="AND">
          <ViewCriteriaRow
            Name="vcrow26"
            UpperColumns="1">
            <ViewCriteriaItem
              Name="InspectionRecordNumber"
              ViewAttribute="InspectionRecordNumber"
              Operator="="
              Conjunction="AND"
              Value=""
              Required="Optional"/>
          </ViewCriteriaRow>
        </ViewCriteria>
      </ViewCriteriaItem>
    </ViewCriteriaRow>
</ViewCriteria>
and this is in the other view object:
<ViewCriteria
      Name="IRSearchCriteria"
      ViewObjectName="gov.nasa.jpl.ocio.qars.model.views.InspectionRecordVO"
      Conjunction="AND">
      <Properties>... </Properties>
      <ViewCriteriaRow
         Name="vcrow7"
         UpperColumns="1">
         <ViewCriteriaItem
            Name="InspectionRecordNumber"
            ViewAttribute="InspectionRecordNumber"
            Operator="="
            Conjunction="AND"
            Required="Optional"/>
      </ViewCriteriaRow>
   </ViewCriteria>
3) I had a query panel and tree table auto-generated by dragging the data control for ONE of the view object data relationship that's exposed in the app module. Then I created a second query panel and tree table the same way but using the data control for the other. I'm hiding one of the query panels permanently and toggling the visibility of the tree tables based on the display mode the user chooses. Both tables have separate bindings and iterators.
This is a portion of the page definition:
<executables>
    <variableIterator id="variables"/>
    <searchRegion Criteria="IRSearchCriteria"
                  Customizer="oracle.jbo.uicli.binding.JUSearchBindingCustomizer"
                  Binds="InspectionRecordVOIterator"
                  id="IRSearchCriteriaQuery"/>
    <iterator Binds="InspectionRecordVO" RangeSize="25"
              DataControl="QARS_AppModuleDataControl"
              id="InspectionRecordVOIterator" ChangeEventPolicy="ppr"/>
    <iterator Binds="Root.QARS_AppModule.PartsVO1"
              DataControl="QarsMasterAppModuleDataControl" RangeSize="25"
              id="PartsVO1Iterator"/>
    <searchRegion Criteria="PartsVOCriteria"
                  Customizer="oracle.jbo.uicli.binding.JUSearchBindingCustomizer"
                  Binds="PartsVO1Iterator" id="PartsVOCriteriaQuery"/>
</executables>
4) I've created a custom queryListener to delegate the query event.
This is in my advanced search jsp page:
<af:query id="qryId1" headerText="Search" disclosed="true"
                  value="#{bindings.IRSearchCriteriaQuery.queryDescriptor}"
                  model="#{bindings.IRSearchCriteriaQuery.queryModel}"
                  queryListener="#{pageFlowScope.SearchBean.doSearch}"
                  queryOperationListener="#{bindings.IRSearchCriteriaQuery.processQueryOperation}"
                  resultComponentId="::resId2" maxColumns="1"
                  displayMode="compact" type="stretch"/>
This is in my backing bean:
public void doSearch(QueryEvent queryEvent) {
      String bindingName = flag
         ? "#{bindings.IRSearchCriteriaQuery.processQuery}"
         : "#{bindings.PartsVOCriteriaQuery.processQuery}";
      invokeMethodExpression(bindingName, queryEvent);
   private void invokeMethodExpression(String expr, QueryEvent queryEvent) {
      FacesContext fctx = FacesContext.getCurrentInstance();
      ELContext elContext = fctx.getELContext();
      ExpressionFactory eFactory = fctx.getApplication().getExpressionFactory();
      MethodExpression mexpr =
         eFactory.createMethodExpression(elContext, expr, Object.class, new Class[] { QueryEvent.class });
      mexpr.invoke(elContext, new Object[] { queryEvent });
When no inspection record number (the only search field so far) is supplied in the query panel, then it behaves correctly. Namely, the tree tables shows all search results. However, when an inspection record number is supplied the tree table that was created with the query panel in use (remember there are two query panels, one of them is hidden) shows a single result (this is correct) while the other tree table (the one with the hidden query panel that isn't in use) shows all results (this is NOT correct).
Is what I'm trying to accomplish even doable? If so, what am I missing?
I'm using JDeveloper 11.1.1.7
Thanks,
Bill

I ended up keeping one query panel permanently visible and the other permanently hidden. When performing a search using the table that has the hidden query panel, I seed the query descriptor for the hidden query panel using the visible query panel's query descriptor and then delegate the request:
   public void doSearch(QueryEvent queryEvent) {
      String bindingName = null;
      if(isIrTableRendered()) {
         bindingName = "#{bindings.IRSearchCriteriaQuery.processQuery}";
      } else {
         seedPartsQueryDescriptor();
         bindingName = "#{bindings.PartsVOCriteriaQuery.processQuery}";
         queryEvent = new QueryEvent(partsQuery, partsQuery.getValue());
      invokeMethodExpression(bindingName, queryEvent);
   private void seedPartsQueryDescriptor() {
      ConjunctionCriterion criterion = irQuery.getValue().getConjunctionCriterion();
      for(Criterion criteria : criterion.getCriterionList()) {
         AttributeCriterion attributeCriteria = (AttributeCriterion)criteria;
         List values = attributeCriteria.getValues();
         String qualifiedName = attributeCriteria.getAttribute().getName();
         int indexOfDot = qualifiedName.lastIndexOf(".");
         String name = indexOfDot < 0
            ? qualifiedName
            : qualifiedName.substring(indexOfDot + 1);
         ConjunctionCriterion partsCriterion =
            partsQuery.getValue().getConjunctionCriterion();
         for (Criterion partsCriteria : partsCriterion.getCriterionList()) {
            AttributeCriterion partsAttributeCriteria =
               (AttributeCriterion) partsCriteria;
            String partsQualifiedName =
               partsAttributeCriteria.getAttribute().getName();
            if (partsQualifiedName.endsWith(name)) {
               partsAttributeCriteria.setOperator(attributeCriteria.getOperator());
               List partsValues = partsAttributeCriteria.getValues();
               partsValues.clear();
               for (int i = 0, count = values.size(); i < count; i++) {
                  partsValues.set(i, values.get(i));
   private void invokeMethodExpression(String expr, QueryEvent queryEvent) {
      FacesContext facesContext = FacesContext.getCurrentInstance();
      ELContext elContext = facesContext.getELContext();
      ExpressionFactory expressionFactory =
         facesContext.getApplication().getExpressionFactory();
      MethodExpression methodExpression =
         expressionFactory.createMethodExpression(elContext, expr, Object.class, new Class[] { QueryEvent.class });
      methodExpression.invoke(elContext, new Object[] { queryEvent });
Then when the advanced/basic button is pressed for the visible query panel, I programmatically set the same mode for the hidden query panel:
   public void handleQueryModeChange(QueryOperationEvent queryOperationEvent) {
      if(queryOperationEvent.getOperation() == QueryOperationEvent.Operation.MODE_CHANGE) {
         QueryMode queryMode = (QueryMode) irQuery.getValue().getUIHints().get(QueryDescriptor.UIHINT_MODE);
         QueryDescriptor queryDescriptor = partsQuery.getValue();
         queryDescriptor.changeMode(queryMode);
         AdfFacesContext.getCurrentInstance().addPartialTarget(partsQuery);

Outer join in view criteria: how to ?

Hello,
I have to create a VO for a LOV. I created in this VO a ViewCriteria to pass variables for the query.
The problem is that for one of this variable I have to set the clause as an outer join.
JDeveloper creates:
SELECT MyView1.Item, MyView2.Code
FROM MyView1, MyView2
WHERE MyView1.ID = MyView2.EXT_ID (+)
AND MyView1.Item = :TheItem
AND MyView2.Code = :TheCodebut I need something like:
SELECT MyView1.Item, MyView2.Code
FROM MyView1, MyView2
WHERE MyView1.ID = MyView2.EXT_ID (+)
AND MyView1.Item = :TheItem
AND :TheCode = MyView2.Code (+)

ADFboy wrote:
this is optional parameter value, in the view criteria windows is this option....
AdfBoyNo, this parameter is not optional because, in the call of the LOV it will be always set.
But the query without the outer join returns too few rows...
I tried to find where to "intercept" this programmatically, but I'm failing doing this. :(
I'll have the same problem with another field, not for a LOV but to get the value of an attribute of a VO.
Even in advanced mode the Where clause can't have parameters...

Set view criteria in ViewObject

Similar Messages

Maybe you are looking for