In af:query component , need to make Match option invisble

Hi,
i am using af:query component and do not want to show the Match with radio button options (All, Any).
Can anyone suggest how to achieve this.

You use view criteria, as this is what af:query is for. You use 'All queryable Attributes' which is an implicit view criteria.
There is no easy way (I don't know one) to remove the 'Match all/any' radio button other than the way Luc described. In your case you have to build a view criteria like the 'All queryable Attributes' to get to the switch in the UI hint tab of the view criteria.
To do this you create a new criteria and add all attributes you want to one group without specifying and literal or bind variable and use an operator like StartWith for strings and equal for numbers. Then uncheck the 'Show Match all Any' checkbox and use this view criteria for your af:query.
Timo

Similar Messages

af:query component - need help

hi
I am implemeting a search page wiht <af:query> component with view criteria. (to be specific drag and drop viewCriteria as query panel with table)
what i observe is that when I do "Add fields" at runtime the compnent moves up and up till it hides the panelHeader and the other fields with no access to it.
After i refresh the screen the component comes back to its normal positon but pushes the table component below it down till its barely visible.
This component seems to be very unstable.
Let me know if there is any workaround without making the screen unstable.

Hi,
You can find some related info here..
Can I achive valueChangeListener in af:query?
and
http://jobinesh.blogspot.com/2011/03/retrieving-viewcriteria-from-custom.html
Thanks,
TK

Passing Item Number as a Parameter takes long time,need to make it optional

Hi,
I am trying to pass Inventory Item as a parameter in the discoverer report and it is taking long time to query the results. I am not sure how to make a parameter optional (Not Required)
Please advice
Thanks,
user12048986
Edited by: user12048986 on Apr 19, 2010 2:54 PM

Hi
In order to use the value ALL in a list of values you have to do two things. These are:
1. Create the LOV like you did with a SELECT 'ALL' FROM DUAL unioned to the real LOV
2. Create a condition that looks for the word ALL
Here's the condition:
COLUMN_VALUE = :Parameter_Value OR :Parameter_Value = 'ALL'
You could also make sure the value is in uppercase using this:
COLUMN_VALUE = :Parameter_Value OR UPPER(:Parameter_Value) = 'ALL'
This way if a user keyed 'all' it would still work.
Best wishes
Michael

Need Information on af:query component

Hi,
I need some information on the <af:query> component in JDev 11g.
When using ADF 11g's new component, ADF Query (af:query) whether the default "All Queryable Attributes" or on other newly defined View Criterias:
1     What are the disadvantages of this component, given that the result-set - without filtering - is large (between 1350 and 1700 rows, approximately).
2     Does it fetch all rows from the database, then performs filtering upon user's entered search criteria – i.e., hitting the "search" button?
3     Is there a way to add client-side validation on the search criteria attributes?
4     In general: What is the best practice to implement a Search Form in ADF 11g
Kindly provide your inputs for the same.
Thanks,
Vineet

user445872 wrote:
Hi,
I need some information on the <af:query> component in JDev 11g.
When using ADF 11g's new component, ADF Query (af:query) whether the default "All Queryable Attributes" or on other newly defined View Criterias:
1     What are the disadvantages of this component, given that the result-set - without filtering - is large (between 1350 and 1700 rows, approximately).
2     Does it fetch all rows from the database, then performs filtering upon user's entered search criteria – i.e., hitting the "search" button? You could tune your VO not to exeute the query by default (i.e., before applying a search criteria)
check this blog for sample: http://andrejusb-samples.blogspot.com/2009/08/jdevadf-sample-oracle-adf-tuning.html
As an other option, you could have a default view criteria applied and executed to filter to result set if it is applicable for your usecase.
3     Is there a way to add client-side validation on the search criteria attributes?I'm not sure about this though.
4     In general: What is the best practice to implement a Search Form in ADF 11g
In addition check this sample as well. It might be of help: http://andrejusb-samples.blogspot.com/2009/09/jdevadf-sample-programmatical-reset-for.html
regards,
~K

Af:query component and persisting preference to database

I am using af:query component for search functionality and that component has an saving preference option to store the preference in session. I would like to store/persist the preference to database and retreive them and show to the user when they come next time.
Could you please let me know, how to accomplish this?
Thanks

Ejsp2000,
In order to do this, you need MDS, which didn't make it into this release of JDeveloper.
I asked this very question a month or so back - you may be able to find it by searching.
John

Customizing af:query component?

Hello friends,
Is it possible to customize af:query component. For example i need to move "search", "reset","save" buttons to the toolbar of the component and change the background of the toolbar. Also i have a request to hide that "+/-" thing which make able user to collapse or disclose af:query form.
Is it possible or only way to achieve this is to create my own search mechanism - what i can imagine could take a while?
thanks in advance

Hi,
as far as color coding goes, you can use skinning for this. Look for "af:query component" in http://download.oracle.com/docs/cd/E15523_01/apirefs.1111/e15862/toc.htm
This should also allow you to hide the +/- icons. However, it does not allow you to move buttons
Frank

View of one component need to be used in another component.

Hi Experts,
I have created a view in component BP_DATA . I want to use this view in component "BP_HEAD". Can anyone please help me with the steps needed to make the view available in BP_DATA. Do i need to do any type of binding for this.

Hello Ansal,
For using BP_DATA/yourview in component BP_HEAD, first you will have to expose BP_DATA view in component interface. Then you can access that view in BP_HEAD by creating component usage. Once you add the view of BP_DATA in component usage of BP_HEAD, it will be available as a normal view in this component.
-Regards

Need to Make end customer field mandatory in sales order form.

I need to make end customer field mandatory when sales channel entered as some value...
for this i have used when validate record on order form
when i enter a value in sales channel as desired value the form is getting saved automatically and the field is getting mandatory
but my requirement is to make field mandatory and then to save the order.
let me know the sequence how it works if any one knows.

Sanni,
>
when i enter a value in sales channel as desired value the form is <b>getting saved automatically</b> and (then) the <b>field is getting mandatory</b>
but my requirement is to make field mandatory and then to save the order.
>
Which trigger are you using to do the "getting saved automatically'?
Does this trigger fire before the trigger that is making the field mandatory?
Regards,
PS: Is this an Oracle EBS query? If yes, this is the wrong forum
Edited by: Prabodh on Jun 14, 2012 4:48 PM

Incorrect operators in af:query component

We have created a search popup using af:query component based on a view criteria.
The view criteria uses two string[varchar2(60) in EO] attributes named "Name" and "Owner".
TerritorySearchViewCriteria
Group
Name CONTAINS :BindTerritoryName -- String in VO, Varchar2(60) in EO
AND Owner CONTAINS :BindOwnerName -- String in VO, varchar2(360) in EO
Issue:
The operators drop down shows some irrelevant search operators(not meaningful to strings) such as "BETWEEN",
"NOT BETWEEN", "BEFORE", "AFTER", "ON OR AFTER" and "ON OR BEFORE". Because of this we are seeing some unexpected
search results when this operators are used for searching.
On looking at the Bali site and BLAF guidelines page it clearly states that the list of operators for string are
"EQUALS", "NOT EQUALS", "STARTS WITH", "ENDS WITH", "CONTAINS", "DOES NOT CONTAIN", "LIKE", "IS BLANK" and "IS NOT
BLANK".
Bali link: http://dadvmc0454.us.oracle.com:9002/faces-11.1.1.2.0/faces/components/query.jspx?_afrLoop=19876843626481699&_afrWindowMode=0&_afrWindowId=null
BLAF guidelines: http://blafstaging.us.oracle.com/blafSite/guidelines5/search.html#queryPanelCond
Attribute Definition in TerritoryEO:
<Attribute
Name="Name"
IsNotNull="true"
Precision="60"
ColumnName="NAME"
Type="java.lang.String"
ColumnType="VARCHAR2"
SQLType="VARCHAR"
TableName="MOT_TERRITORIES">
Attribute definition in TerritoryVO:
<ViewAttribute
Name="Name"
IsNotNull="true"
PrecisionRule="true"
EntityAttrName="Name"
EntityUsage="Territory"
AliasName="NAME">
Query component in ManageTerritories.jsff:
<af:query id="qryId1" headerText="#{acrGenBundle['Header.Search']}"
disclosed="true"
value="#{bindings.TerritorySearchQuery.queryDescriptor}"
model="#{bindings.TerritorySearchQuery.queryModel}"
queryListener="#{backingBeanScope.ManageTerritoriesBean.onTerritorySearchQuery}"
queryOperationListener="#{bindings.TerritorySearchQuery.processQueryOperation}"
resultComponentId="::pc2:resId1"
saveQueryMode="hidden"
modeChangeVisible="false"
conjunctionReadOnly="true"
styleClass="AFStretchWidth"/>
Is there a way to eliminate the operators which does not make sense for String type.
Thanks,
Sekar

As per the guidelines mentioned for String, You could remove the unwanted operators from the view criteria item.
The example below shows - how the unwanted operators namely BETWEEN & NOTBETWEEN could be removed.
For more details, look into the following section 27.3.3 in the developer's guide:
http://download.oracle.com/docs/cd/E15523_01/web.1111/b31974/web_search_bc.htm#CIHIDGGC
Sample:
<ViewCriteria
Name="EmployeesVOByFirstNameOrLastName"
ViewObjectName="model.views.EmployeesVO"
Conjunction="AND">
<Properties>
<CustomProperties>
<Property
Name="displayOperators"
Value="InAdvancedMode"/>
<Property
Name="autoExecute"
Value="false"/>
<Property
Name="allowConjunctionOverride"
Value="true"/>
<Property
Name="showInList"
Value="true"/>
<Property
Name="mode"
Value="Basic"/>
</CustomProperties>
</Properties>
<ViewCriteriaRow
Name="vcrow0"
UpperColumns="1">
<ViewCriteriaItem
Name="FirstName"
ViewAttribute="FirstName"
Operator="CONTAINS"
Conjunction="AND"
Value=""
Required="Optional">
*<CompOper*
Name="Category"
ToDo="-1"
Oper="BETWEEN"/>
*<CompOper*
Name="Category"
ToDo="-1"
Oper="NOTBETWEEN"/>
</ViewCriteriaItem>
<ViewCriteriaItem
Name="LastName"
ViewAttribute="LastName"
Operator="CONTAINS"
Conjunction="OR"
Value=""
Required="Optional"/>
</ViewCriteriaRow>
</ViewCriteria>
Thanks,
Navaneeth

Add custom field to af:query component?

Anyone had any experience overriding af:query copmonent? I need to add my custom search field (to query component), which would have a search icon next to it, and on click, a popup widow would open containing my custom task flow where I could select a record with certain value and on return that custom field (in query component) would get populated with selected value. I hope I'm being clear. Please point me to any useful information. Is that even possible? I use JDeveloper 11.1.2.3.4.0 Regards, Marko

Hi,
af:query is a component that comes as is. Its not designed for customization in that you can add your own fields. If you have a requirement for this then
1. expose a method on the VO Impl or AM Impl that expect arguments (your query parameters)
2. Use the arguments to populate bind variables used by a ViewCriteria
3. Apply the View Criteria to the View Object
4. Execte the View Object
5. Drag and drop the method from the DC panel as a parameter form
6. Ensure the result table PartialTrigger property is pointing to the button ID of the parameter form
7. Change whatever UI component you want to change in the parameter form
This gets you going ...
Frank

Information Broadcasting & Archiving: Query reports need to be Archived

Hi All,
The requirement is that , we need to broadcast query reports in Bex 7.0 to be archived as a pdf.
Please note that this is not Data archiving. We need to archive only query reports.
We need to make sure that pdf gets generated in Background and report selections variant can be used in Background.How can we achieve this?
Alternatively ,Please suggest useful articles, that will be of help in this.
Thanks in Advance ,

archiving data is plausible -
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/events/asug-biti-03/sap%20bw%20archiving%20and%20data%20aging%20strategies
Not sure why you want to archive the reports in PDF, also at what point?? is it on the application sever ???
Hope it Helps
Chetan
@CP..

Programmatically Load Query Component on Page Load

Hi All.
We have a requirement in which we need to populate the fields of a query component and execute the query...upon loading of the page.
Our use case:
We have a page in which there is an analytic showing counts of requests in different status (i.e. Open, Closed, In Process).
Status Count
==== ====
Closed _5_
Open _3_
In Process _6_
When the user clicks on the count (which is a hyperlink) we want to take them to the "Search for Requests" page with the criteria filled out and the query automatically executed. For example, if the user clicks on the count of "5" (for Closed)....they will be transferred to the "Search for Requests" page. The query field of "Status" will be defaulted with "Closed" and the query automatically executed (with the 5 requests shown in the result set).
We are using page fragments (.jsff) in bounded ADF task flows.
I am thinking that we need to set up a default activity in the "Search for Requests" task flow that will call the AM Impl method to handle this on the model side but I am unclear on how to programmatically set the criteria that is used in a query component?
Any help is appreciated.
Thanks.
D

In the processRequest of your controller you can invoke a method in the AM which in turn invokes a method in the Search VO which sets the where clause and executes the query.

Af:query component with cascading Lov's

Hi All,
I have Cascading LOV's model setup in Business Components and they work fine in a form or table
but they are not working inside af:query component as there is no autoSubmit attribute on the query component itself
can someone help me to resolve this
Thanks in Advance

I have found a way
using bindings attribute of the query component it was able to go to backing bean on any LOV change in there we need to manually refresh the bindings then it works

Af:query component added field not removed when remove icon is clicked

I have an af:query component on a popup dialog. In advanced mode when I add a field, the new field appears in the searchRegion followed by a red X remove icon. If I subsequently click that remove icon, the query refreshes, the red icon is gone, but the newly added field still remains. The query component is linked to a standard VO query executable in the bindings. There is no custom processing of the value, model, queryListener or the queryOperationListener. In all other respects the query component works fine. The only problem is a newly added field not being removed when the remove icon is clicked. Here's how the component is setup (an added wrinkle is that the query component is hosted in a Declarative Component, so that makes this code a little harder to decipher).
Does anyone know where I should start looking for this? Hopefully I don't have to implement my own queryOperationListener.
JDev version is Build JDEVADF_11.1.1.4.0_GENERIC_101227.1736.5923
--- snippet from the page fragment ------
<af:popup id="frmsLstPU" contentDelivery="lazyUncached">
<af:dialog id="d1" type="ok"
styleClass="AFStretchWidth" resize="on"
stretchChildren="first" contentWidth="840"
contentHeight="480"
title="#{UnifiedResourceBundle['FORMSLIST.DIALOG.TITLE']}">
<idmkr_adf:Correspondence_Formslist_Query idmkr_query_model="#{bindings.FormVOFlatQueryCriteriaQuery}"
idmkr_table_binding="#{viewScope.FormsListBacking}"
idmkr_table_model="#{bindings.FormVOFlatQuery1}"
idmkr_bindings="#{bindings}"
idmkr_resourcebundle="#{preferences}"
idmkr_printStreamBean="#{viewScope.FormsList}"
id="cf1">
</idmkr_adf:Correspondence_Formslist_Query>
</af:dialog>
</af:popup>
-- snippet from the Correspondence_Formslist_Query declarative component ------
<af:query id="qryId1"
headerText="#{UnifiedResourceBundle['FORMSLIST.QUERY.SEARCH.TEXT']}"
disclosed="true"
value="#{attrs.idmkr_query_model.queryDescriptor}"
model="#{attrs.idmkr_query_model.queryModel}"
queryListener="#{attrs.idmkr_query_model.processQuery}"
queryOperationListener="#{attrs.idmkr_query_model.processQueryOperation}"
resultComponentId="::resId1" displayMode="default"
styleClass="AFStretchWidth"
rows="4" maxColumns="2"/>

I have changed the contentDelivery from "lazyUncached" to "immediate" and the same problem occurs. Thank your for your suggestion.

Is it possible to use the af:query component with programmatic VOs?

My understanding is that the view criteria in a normal SQL-based VO are used to add WHERE clauses to the VO.
Since programmatic VOs do no have this capability, is there something I need to override in the view object implementation class to support the view criteria that will be established by the af:query component?
Does someone have an example of how this might be done?
Thanks, -Klaus

Unfortunately no. The remote control will work, but the radio will not.
The radio only works with the iPod video and the nano.

In af:query component , need to make Match option invisble

Similar Messages

Maybe you are looking for