Hiding Query Region Using PPR

Hi All,
Have used POV to create a boolean trannsient attribute and the value for that is changing perfectly, but when I'm trying to set it as value for Rendered property of Query Region, that is not working as expceted, not able to hide Query Region
the rendered property is set as below:
${oa.QueryRNPVO1.QueryRNRendered}
QueryRNPOV1 is the POV and QueryRendered is the boolean attribute of it.
Please help.
Regards
Ritesh

Hi,
Can you paste the code here, how are you handling it.
Thanks
Saurabh

Similar Messages

How to get handle of go, clear button in query region.

Hi: I have a search page built using query region, I need to make an API (method) call on clicking on "Go" button.
I tried the following as found in OA Framework discussion forum, but observed that "go" is always true in processFormRequest method and always false in processRequest method.
I did check the methods of OASubmitButtonBean also, but unable to find out how exactly I get "the handle of go button click event" in this case to handle my requirement.
Any idea if its possible or not, and if yes, then how?
OAQueryBean queryBean = (OAQueryBean)webBean.findChildRecursive("QueryRN");
String idGo = queryBean.getGoButtonName();
OASubmitButtonBean go = (OASubmitButtonBean)queryBean.findChildRecursive(idGo );
I did also try to add my buttons in the query region, which work as I require, but in that case I need to hide existing go, clear buttons (which are added by default) in query region. That also doesn't work, as in processRequest method "go" is always false, and in processFormRequest I cannot call "go.setRendered(false);".
Also, button should be disabled even on first loading of page also. Can anyone help?
Regards,
Anvita.

modified code further as follows --
OAQueryBean queryBean = (OAQueryBean)webBean.findIndexedChildRecursive("QueryRN");
String idClear = queryBean.getClearButtonName();
OASubmitButtonBean clear = (OASubmitButtonBean)queryBean.findChildRecursive(idClear);
String idGo = queryBean.getGoButtonName();
OASubmitButtonBean go = (OASubmitButtonBean)queryBean.findChildRecursive(idGo);
System.out.println("I wish it works in +++++++++++++++++++++++++ " + idClear + " xxx " + idGo);
if (pageContext.getParameter("idGo") != null)
System.out.println("I wish it works in GO +++++++++++++++++++++++++ ");
if (pageContext.getParameter("idClear") != null)
System.out.println("I wish it works in Clear +++++++++++++++++++++++++ ");
if (pageContext.getParameter("go") != null)
System.out.println("I wish it works in GO button +++++++++++++++++++++++++ ");
if (pageContext.getParameter("clear") != null)
System.out.println("I wish it works in Clear button +++++++++++++++++++++++++ ");
if (go != null)
System.out.println("I wish it works in GO button direct +++++++++++++++++++++++++ ");
if (clear != null)
System.out.println("I wish it works in Clear button direct +++++++++++++++++++++++++ ");
=============================================
and output print is always the following even if i click on button or not (like select some LOV, or perform PPR action) .. hence it doesn't allow me to catch go button click event .. Please advice ..
output PRINT --
I wish it works in +++++++++++++++++++++++++ clearButton xxx customizeSubmitButton
I wish it works in GO button direct +++++++++++++++++++++++++
I wish it works in Clear button direct +++++++++++++++++++++++++

Problem with SQL query region source containing OLAP clauses

Hi team,
I believe I found a bug when HTMLDB validates the SQL Query in a report region.
My query includes an ORDER BY clause within a windowing function and HTMLDB refuses to accept the source owing to the presence of the ORDER BY and the column heading sort preference.
Clearly the order-by in a window function has little to do with the column heading sort, but this error prevents me from updating the conditional display item in the page definition.
Note also that the page was imported smoothly from the 1.5 version, so probably the region source is not checked at that time, but only when you update it "manually".
So, in the end, if I don't change anything the page works because the sql query is assumed to be correct but unfortunately I need to change the condition and I cannot.
The problem shows up in page 126 of app 21670, SQL query region.
Bye,
Flavio
PS: may be I can work around this by using the pl/sql function returning the sql query.

Flavio,
We're aware of this problem. For now, your workaround is described in this thread:
HTMLDB 1.6 and "order by" in analytic functions
Sergio

Can we add button in query region along with go and clear

Hi Friends,
i have a requirement as below steps-
1)i have developed search pgae by using query regiion
2) in pgae,first we have search items,go and clear(submit buttons), table region.
3)here go and clear buttons came automatically.
4) i can able to add button in front of the page and end of the page.
4) my requirement is i need to add one more button along with go and clear(here go and clear button are in between search items and table region) .
5)i am not able to add button along with go and clear.
Can any one know how to do this--
Thanks in Advance
vamshi

Hi Vamshi,
You can not create extra buttons in Standard Query region.
Alternatively you can create your custom region for the search and there you can add a button. If you don't need advanced region, you can create the custom region in place of standard one.
Anoop

Query Region causes error in Popup Region ....

Hi
(12.1.3 custom development)
I am opening a (parameterized) popup region on a button press (so far so good).
I want to put a simple query region in the popup region (results based search) but the page will not render ->
## Detail 0 ##
java.lang.NullPointerException
at oracle.apps.fnd.framework.webui.OAQueryHelper.renderSimpleSearch(Unknown Source)
at oracle.apps.fnd.framework.webui.OAQueryHelper.processRequestAfterController(Unknown Source)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(Unknown Source)
at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(Unknown Source)
at oracle.apps.fnd.framework.webui.OAQueryHelper.processRequest(Unknown Source)
at oracle.apps.fnd.framework.webui.beans.layout.OAStackLayoutBean.processRequest(Unknown Source)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(Unknown Source)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(Unknown Source)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(Unknown Source)
at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(Unknown Source)
at oracle.apps.fnd.framework.webui.beans.layout.OAStackLayoutBean.processRequest(Unknown Source)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(Unknown Source)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(Unknown Source)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(Unknown Source)
at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(Unknown Source)
at oracle.apps.fnd.framework.webui.beans.form.OAFormBean.processRequest(Unknown Source)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(Unknown Source)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(Unknown Source)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(Unknown Source)
at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(Unknown Source)
at oracle.apps.fnd.framework.webui.beans.layout.OAHeaderBean.processRequest(Unknown Source)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(Unknown Source)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequestChildren(Unknown Source)
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(Unknown Source)
at oracle.apps.fnd.framework.webui.OAWebBeanContainerHelper.processRequest(Unknown Source)
at oracle.apps.fnd.framework.webui.beans.OABodyBean.processRequest(Unknown Source)
at oracle.apps.fnd.framework.webui.OAPageBean.processRequest(Unknown Source)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(Unknown Source)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(Unknown Source)
at oracle.apps.fnd.framework.webui.OAPageBean.preparePage(Unknown Source)
at _OA._jspService(_OA.java:71)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:59)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:462)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:594)
I don't know what it is referring to with 'Unknown Source', I 've tried with a couple of different VOs, same result ...

hi,
I'm not sure but once check your DBC file...are you using latest DBC file:
Oracle Apps R12 , DBC file is located at $INST_TOP/appl/fnd/12.0.0/secure not under $FND_TOP
Check once.
Regards
Mahesh

Clear the data region using Maxl

Hi,
I am trying to clear the data region using Maxl query, I am getting error like: Dynamic members not allowed in data clear region specificaion.
+alter database 'PGSASO'.'ASOPGS' clear data in region 'CrossJoin(CrossJoin({[Actual]},{[FY11]}),{[Inputs].Levels( 0 ).Members})';+
(Inputs( not a dynamic member, parent of this meber is a dynamic) comes under Account dim).
I have tried the below code also(Syntax error in input MDX queryon line 1 at token ',').
alter database 'PGSASO'.'ASOPGS' clear data in region 'CrossJoin([Inputs].Levels(0), CrossJoin({[ACT]},{[FY11]}))';
Can anyone do let me know if there is any syntax error or alternate function would be available for clearing level-0 members/descendants under Dynamic parent...
Thanks,
Bharathi

There is no syntax error in your statement. The problem is you input dimension(I guess) has some members with formulas on them and the clear statement does not allow those members to be in the clear. Ther ware a couple of ways around it. seperate out the members with formulas under a different parent and then modify the crossjoin to only pick up the level zero members that are not in that parent or you could put a UDA on formula members and use the exclude command to exclude anything with that UDA

OA Query Region: How to remove "like" clause in background query

I have an <oa:query/> region that has an id field as a parameter.
The problem is if I enter "534" it will run a query with a where clause of "COLUMN like '534%' ", which is not what I want.
I want it to search for an exact match and not a partial match. Is there a way to do this using the standard attributes (without having to build the where clause manually)?
TIA,
-C

Hi,
You can specify the Data type of the field as Number..then the Query region will use '=' instead of 'LIKE'.
Arun

OA Query Region shows previous search results when moving between pages

Hello All,
I have a custom OA Page which has a query region based on a LOV for searching device names. The problem I am facing is once device name is searched and I go to another page through the quick links and come back to same Search Device page, it shows the previous searched results. I am not retaining AM for any page navigation.
Things I have already tried :
1 . I have tried refreshing VO by using clearcache and reset methods on VO.
2. Get the Go button from the query region in ProcessFormRequest and on Go button click I use forwardImmediatelyToCurrentPage. And in Process Request method I am querying the results manually when Go button is clicked. Otherwise I am manually making the where clause condition 1=2 and ensuring that the VO does not return any rows.
But still I am not able to get rid of the issue.
The code used is pasted below for your reference. It is urgent. Can you please provide any pointers.
public void processRequest(OAPageContext pageContext, OAWebBean webBean)
super.processRequest(pageContext, webBean);
try
VpaAdminAMImpl am = (VpaAdminAMImpl)pageContext.getApplicationModule(webBean);
TkvpaDeviceSearchVOImpl deviceAll = am.getTkvpaDeviceSearchVO1();
deviceAll.clearCache();
deviceAll.reset();
deviceAll.setWhereClause("1=2");
deviceAll.setWhereClauseParams(null);
String query = deviceAll.getQuery();
System.out.println("getSearchResult query :="+query);
deviceAll.executeQuery();
OAQueryBean queryBean = (OAQueryBean)webBean.findChildRecursive("region1");
String goAction = queryBean.getGoButtonName();
if(pageContext.getParameter(goAction) != null)
getSearchResult(am, pageContext, webBean);
catch(Exception ex)
throwException("SearchDeviceCO.processRequest",ex);
public void processFormRequest(OAPageContext pageContext, OAWebBean webBean)
super.processFormRequest(pageContext, webBean);
String action = pageContext.getParameter(EVENT_PARAM);
OAQueryBean queryBean = (OAQueryBean)webBean.findChildRecursive("region1");
String Go = queryBean.getGoButtonName();
System.out.println(pageContext.getParameter(Go));
if(pageContext.getParameter(Go) != null)
pageContext.forwardImmediatelyToCurrentPage(null,false,"N");
public void getSearchResult(VpaAdminAMImpl am, OAPageContext pageContext, OAWebBean webBean)
try
String device = pageContext.getParameter("deviceSearch");
StringBuffer sb = new StringBuffer();
if(device != null && device != "")
sb.append(" DEVICE_NAME = '");
sb.append(device);
sb.append("'");
String sql = sb.toString();
TkvpaDeviceSearchVOImpl deviceAll = am.getTkvpaDeviceSearchVO1();
deviceAll.setWhereClause(sql);
deviceAll.setWhereClauseParams(null);
String query = deviceAll.getQuery();
System.out.println("getSearchResult query :="+query);
deviceAll.executeQuery();
}catch(Exception e)
e.printStackTrace();
Thanks in Advance,
Abhishek Mishra

Hi Anand,
The getSearchResult method also does the same thing. I have also tried to remove the dependency on getSearchResult and wrote the same code in ProcessRequest() but still it does not solve the problem.
In fact, I have ensured that the VO does not contain any records and have checked these by using SOPs and debug in JDEV. The interesting point is the VO does not have any records but still the previous search data and search criteria is shown when we navigate to the page. Printed the query just before performing execute query and that query does not return any records. Also tried printing something if there are any records in the VO by using vo.hasNext().
Data gets stored somewhere and it is shown when the page is navigated from other page. FYI, this page is accessed from quick links and there are other pages also in the quick links and when we navigate between these pages we get to see the previous search results. Tried methods clearCache(), reset() on VOs but still unsuccessful.
Not even that I thought that the VO may be corrupted in some sense so I created a new VO instance in the AM and then used newly created VO instance in the query region. But still no luck.
Any pointers will be appreciated.
Thanks in Advance,
Abhishek

Query Region (autoCustomizationCriteria) search criteria issue

Hi All,
In my search page I have used a Query Region with Construction Mode as autoCustomizationCriteria. Fot this regionin in Simple search panel I have 3 dropdowns and 2 Date Fields(OAMessageDateFieldBean) which in turn are mapped with related simpleSearchMappings fields.
On this page , for search result table as table actions i have a create button which transfers me to create page. On create page I have the same dropdowns and date fields which are there on search page as search criteria.
Now when i create a record , on click of create button records gets created and controls returns back to the search page with this newly created record in the search result table.(by default whenever search page is rendered it shows all records)
The problem here is the search criteria dropdown and date fields gets populated with the values with which a new record was created .
Why these values are getting populated as the page is difference and whenever the VO is querried I am already clearing its cache?
Any suggestions regarding this ?
Thanks and Regards,
Anant Nimbalkar.

Hi RamKumar,
I have tried not to retain the AM and it worked but now there is a different problem.
On create page on click of save button the record gets saved and related message is displayed on search page. (Used to work before i made retail AM flag false)
But now as i have set it to false I am unable to show these messages on the Search page .
Any idea how both these things ie dropdown with no values(on search page) and message can be achieved ?
Thanks and Regards,
Anant Nimbalkar.

Can we handle 'GO' button in a 'QUERY' region

Hi,
Is it possible to handle 'GO' button in a 'QUERY' region.
Can we modify its behavior by a controller kind of thing.
Thanks & Regards,
Swaroop

Straight from the devguide :-)
processFormRequest (OAPageContext pageContext, OAWebBean webBean)
// Make sure that you are in the right panel
OAQueryBean queryBean = (OAQueryBean) webBean;
queryBean.getCurrentSearchPanel();
// Handle the "Go" button click on the simple search panel
if (SEARCH.equals (currentPanel) &&
queryBean.getGoButtonName() != null)
// retrieve your item and process it here.
String value = pageContext.getParameter (<projectIdSimpleSearch>);
// Build the appropriate where clause for projectIdSimpleSearch
// and set it on your vo and execute its query
// using the initQuery method.
// Handle the "Go" button click on the advanced search panel
if (ADVANCED_SEARCH.equals (currentPanel) &&
queryBean.getGoButtonName() != null)
// retrieve your item and process it here.
String value = pageContext.getParameter(<projectIdAdvSearch>);
// build the appropriate where clause for projectIdAdvSearch
// and set it on your vo and execute its query
// using the initQuery method.
Thanks
Tapash

Query Region - Changing "Go" Button

Using JDeveloper 10.1.3.3 with R12.
I was going through the tutorial and I completed the "Search" tutorial. After I was done, I wanted to customize it and play around with it and I'm trying to change the "Go" button to something different, but I can't seem to find where to change the text of the button.
I guess because when you tell it to make a query region and search panel etc it automatically puts in those buttons? But how do I change the text of the buttons.
Thank you in advance.
Edited by: Pierre on Jun 14, 2012 12:09 PM

Pierre,
Yes this is possible. The trick here is to not start with the webBean, but the OAPageLayoutBean. Also you need to attach this controller as the controller of the table beneath your query region so that when it is called, the GO button exists.
Here is the code (presume simpleSearchRN is the name of your query region, change to match your query region name):
OAPageLayoutBean pl = (OAPageLayoutBean) pageContext.getPageLayoutBean();
OAQueryBean qb1 = (OAQueryBean)pl.findChildRecursive("simpleSearchRN");
OASubmitButtonBean sb = (OASubmitButtonBean) qb1.findChildRecursive(qb1.getGoButtonName());
sb.setText("SmartyPants");
Hope this helps.
Kristofer Cruz

Go button in View Panel of Query Region

Hi,
I have a search page uses Query Region, and query region includes Simple Search Panel and View Panel, I understand to get the id of the Go button in Simple Search Panel, the method is: queryBean.getGoButtonName().
How can get the id of Go button in View Panel? In dev guide, it says: pageContext.getPersonalizeGoButtonName(), but this method gives compile error.There is no this method in javadoc of pageContext.
Can you please help?
thanks
Lei

Try queryBean.getPersonalizeGoButtonName()

SubTab region under Query Region not consistent

Hi,
I have to query a table with 10 columns.Insted of showing all 10 columns in a horizontally scrollable page ,I am trying to show 5 columns in a subTab and other five in 2nd subtab.
I created a 'Query' region with ACC , under that created a SubTab region with 2 stacklayout .Each Stack layout have its own result table(with same VO) with the Data columns I need to display.
The problem is when you switch between Subtabs, the 'SubTab2' queries all records. SubTab1 always looks at query criteria and queries only that meets the criteria.
'SubTab2' queries correct records only when u select 'subtab2' and the press 'GO' button in search panel. If u then press 'SubTab1' and agian 'SubTab2' , it will query all records.
Why is 2nd subtab behaving this way , any thoughts ,suggestions on how to over come this?
Thanks
Sudeep

Hi Tapash,
There was no code under formrequet , however I was able to overcome it by setting a new controller and using code following to render the whole web bean initially.
setAttributeValue(MODE_ATTR, SUBTAB_FORM_SUBMISSION_MODE);
Thanks
Sudeep

How to set focus on a textinput/poplist using PPR

HI,
Is it possible to use PPR to set focus on a Text input or Poplist.
if Yes, which attribute in the UI Item we need to use?
will the attribute 'Access Key' work for the same?
If PPR is not an option then getting a java bean for the UI Item is the only option?
Thanks,
Gowtam.

Gowtam,
No, the two basic differences between PPR and fire action!
1)Fire action submit the entire OA Page Form elements, while PPR only refreshes the form components of that particular region.
2)When PPR event is done, framework neglects any other action done on the page.
Now, like your basic question, why should u use PPR event ?Instead y not firaction always?
The reason is the very first defination of PPR.If i have n number of items on my page, if I define every action as fire action after each event page will refresh, so even for a small update like vanishing a field, i have to refresh the entire page which will be unusual for the user because it will take some time to load if page has some heavy components like hgrids , tables etc. Thats y we prefer PPR event over fire action in case of individual events, which is much fast, refreshing only particular form items.
In standard j2ee web applications, the same is done using DHTML and javascript.
I hope i am clear.
--Mukul

Query Region

Hi ,
I have a search page using Query Region (include Simple Search Panel - true, include View Panel - true), now every time when I run the page, I see the view panel first, then after clicking 'Simple Search' button, I can see the Simple Search Panel. I want to see Simple Search Panel as default instead of View Panel when running the page, how it can be done?
thanks
Lei

What happens with include View Panel - false ?
--Shiv

Hiding Query Region Using PPR

Similar Messages

Maybe you are looking for