LOV Validation in Advanced Search

Hello,
We would like to use the LOV validation feature, but it only works in data-entry screens, not in the advanced search screens... Is it a known limitation or am I doing something wrong?
Thank you,
Igor

Sorry Igor, we overlooked your initial post.
LOV validation is intentionally turned off in search items as it would prevent you from using wildcard searches.
Steven Davelaar,
JHeadstart Team.

Similar Messages

Issue with programmatically created LOV on Advanced Search Screen in OCO.

Hi All,
I am trying to create a LOV programmatically on Advanced search screen of Oracle Customer's Online module for the country field present there, i have extended a controller and
in it i am carrying out the creation for this.
i am using the below code to do this.
i am able to access the particular rowlayout bean and code below is starting after that.
OARowLayoutBean CountryRowLayoutBean =
                        (OARowLayoutBean)RgtColTableLayoutBean.getIndexedChild(8);
                    if (pageContext.isLoggingEnabled(PROCEDURE))
                        pageContext.writeDiagnostics(this,
                                                     "CountryRowLayoutBean: " +
                                                     CountryRowLayoutBean,
                                                     PROCEDURE);
                    int CountryRowLytChldCount =
                        CountryRowLayoutBean.getIndexedChildCount();
                    if (pageContext.isLoggingEnabled(PROCEDURE))
                        pageContext.writeDiagnostics(this,
                                                     "CountryRowLytChldCount : " +
                                                     CountryRowLytChldCount,
                                                     PROCEDURE);
                    OAMessageTextInputBean CountryMsgTxt =
                        (OAMessageTextInputBean)CountryRowLayoutBean.getIndexedChild(2);
                    if (pageContext.isLoggingEnabled(PROCEDURE))
                        pageContext.writeDiagnostics(this,
                                                     "CountryMsgTxt : " +
                                                     CountryMsgTxt,
                                                     PROCEDURE);
                    CountryMsgTxt.setRendered(false);
                    OAMessageLovInputBean CountryLOV =
                        (OAMessageLovInputBean)createWebBean(pageContext,
                                                             LOV_TEXT, null,
                                                             MatchRuleAttrId); //MatchRuleAttrId - the fields are rendered through DQM so, this is the Id for the text input , same is taken as id for LOV, to enable search later.
                    if (pageContext.isLoggingEnabled(PROCEDURE))
                        pageContext.writeDiagnostics(this,
                                                     "CountryLOV : " + CountryLOV,
                                                     PROCEDURE);
                    CountryRowLayoutBean.addIndexedChild(CountryLOV);
                    Integer webBeanRegionAppId =
                        (Integer)webBean.getAttributeValue(REGION_APPLICATION_ID);
                    CountryLOV.setAttributeValue(REGION_APPLICATION_ID,
                                                    webBeanRegionAppId);
                    // Specify the path to the base page.
                    CountryLOV.setAttributeValue(REGION_CODE,
                                                    "/oracle/apps/imc/ocong/search/webui/ImcSearchPage");
                              CountryLOV.setAttributeValue(LOV_REGION_APPLICATION_ID,
                                                    webBeanRegionAppId);
                    // Specify the LOV region definition.
                    CountryLOV.setLovRegion("/oracle/apps/ar/hz/address/webui/HzCountryLOV",
                                               webBeanRegionAppId.intValue()); //Standard LOV region used
                    // Validation should be enabled for LOVs unless it's essential for the field to allow a partial value (in a "Search" region, for example).
                    CountryLOV.setUnvalidated(false);
                    CountryLOV.setAttributeValue(SELECTIVE_SEARCH_CRITERIA,
                                                    true);
                    CountryLOV.setAttributeValue(SEARCH, true);
                    // Configure the LOV mappings.
                    // Note that you must call this method after you add the messageLovInput item
                    // to the web bean hierarchy.
                    // base page item
                    // lov item
                    // direction
                    if (pageContext.isLoggingEnabled(PROCEDURE))
                        pageContext.writeDiagnostics(this,
                                                     "webBeanRegionAppId : " +
                                                     webBeanRegionAppId,
                                                     PROCEDURE);
                    if (pageContext.isLoggingEnabled(PROCEDURE))
                        pageContext.writeDiagnostics(this,
                                                     "MatchRuleAttrId : " +
                                                     MatchRuleAttrId,
                                                     PROCEDURE);
                    CountryLOV.addLovRelations(pageContext,
                                                  MatchRuleAttrId,
                                                  "TerritoryShortName",
                                                  LOV_RESULT,
                                                  LOV_REQUIRED_NO); // base page item
                    // lov item
                    // direction
                    CountryLOV.addLovRelations(pageContext,
                                                  MatchRuleAttrId,
                                                  "TerritoryShortName",
                                                  LOV_CRITERIA,
                                                  LOV_REQUIRED_NO);
I am facing the issue that the torch icon is visble on the screen but when i click on it, it does not display the LOV region and a blank page saying website declined to show the page is displayed.
Please suggest what needs to be added that i am missing right now.
Thanks,
Mayank

on the first option I mean you can add new region programaticaly like this on Processrequest
            OAStackLayoutBean newLocationLovs=
                (OAStackLayoutBean)createWebBean(pageContext
                                                    ,"/yandex/oracle/apps/csi/instance/location/webui/YaLocationLovsRN"
                                                    , "xxnewLocationLovs"
                                                    ,true);
              webBean.addIndexedChild(newLocationLovs);

How can I get a LOV to work in the advanced search area

I am using JHeadstart 10.1.3.3.
We are doing a LOV lookup on User-id. When the user selects a user-id or just starts keying in a user-id I have my Jheadstart code to pull in the full-name whenever the client selects a new user-id or starts keying a userid.
Under UserId we have the following definition
PersonIdentitiesLOV
UserId <= UserId
FullName <= CombinedName
We set up PersonIdentitiesLOV so that "Use LOV for validation" is set to true.
When I tested my code, in the advanced search this is what happened:
1) When the client selects a user-id the FullName field gets populated
2) When the client just keys in the user-id then the FullName DOES NOT get populated.
Someone told me that there is a bug in JHeadstart in 10.1.3.3 where if you turn on the "Use LOV for validation" then it does not get executed in the Advanced Search.
How do I get around this problem.
If this does not work then how would it be best to display the full name whenever someone keys in a user-id. We are using this full name display for auditing purposes at the cashiers wicket whenever someone keys in a userid and does not recognize the person. We want the full name displayed along with userid for verification purposes.
Any idea on how to get this working?

This is not a bug, it is intended behavior.
In search fields you might want to search for parts of the name, using a wildcard, that's why the auto-complete is not working there.
If an end user wants to search the complete name, he can use the LOV to pick a value.
Steven Davelaar,
JHeadstart Team.

LOV in Advanced Search Mode Problem

Hi all,
I have a strange problem with LOV!.
In advanced search of our pages, sometimes we used LOV.
As a normal way, we used two entities for the whole page, one as updatable
one, and another which is referenced in LOV and I defined that as reference.
After choosing a value from LOV, I want to assign its return values (from
selected row) to other fields. The returned values from LOV that are comming
from updatable entity is available and I could access them, but I can not see
the returned values from the reference entity.
At the end, I repeat that our LOV is working now for create mode and our problem with that is only in Advanced Search mode.
Thanks for ur helps:)

Hi Nasser2,
You could try to make the attribute in the reference entity that you want to put a new value in, updateable.
I guess you don't see the return value in that attribute in advanced search, because the VO-attr is readonly (which makes sense, because it is a reference-attribute!).
Regards
Evert-Jan
JHeadstart Team

Textfields in advanced search from LOV non-editable

I have a LOV where the textfields in advanced search are always non-editable. When I look into the LOV JSP page, maxlength of the textfields is 0.
One of the textfields uses following attribute:
in EntityObject: attribute "Kuerzel", type "String" (database datatype VARCHAR2(10))
in ViewObject: attribute "DspKuerzel"
in the JHeadstart ADF BC Property Editor from EntityObject and ViewObject the Setting "maximum length" of the attribute is not set (no entry). Jheadstart help says that when maximum length is set to 0 then the corresponding textfield is non-editable. But here it is not set. Is there a solution to this problem?

If you send a testcase to [email protected] and rename extension .zip to .zipped we can investigate why the maximum length is not generated correctly in your situation.
Steven Davelaar,
JHeadstart Team.

LOV Advance Search

We have created an LOV with Advance search option.
When user enter any value in the LOV and tabs out,then it is not performing the search based on entered value. Instead of that , it is just displaying all records from table.
The problem was occuring in R12 instance. In 11i, it was working fine.

this may sound simple but have you checked the lov mappings... specifaclly the criteria item for the LOV

Reduce advanced search criteria LOV

I have created OAF page with resultsBasedSearch = advanced panel Query Region. In advanced search criteria, I see four values in LOV - "is, is not, after, before". I want to limit options to "is" and "after". Is it possible to do this? If so, can you tell me in detail how?

Hi.
please try put your locale en tag view.
<f:view locale="it">
in Jdev 11.1.1.4 works!!

Adding Data through LOV when LOV validation fails to bring row

Question on Adding data to LOV:
Just like in form 5(Professional Forms), Is there a way to dynamically insert the row to add data if the data entered is not in the LOV? I have searched forum and looked at Dev Guide but didn't find any notes. One way is making "AutoValidation" false so LOV will not fire and validate, THEN upon SAVE just commit trx. Will this work? or Is there a better thought. Thanks

Set the Disable Validation property of the LOV Item to "True"
Thanks,
Kumar

I am having problems using Firefox with Ebay in the last 10 days. The advanced search link is dropping off the page and there is no way to access it now.

I have been using Firefox and Ebay for at least 12 years with no problems whatsoever. But in the last 10 days I have been having trouble with the Advanced Search link disappearing from the page on Ebay. If I do a search from the Ebay home page it will show the results, but the Advanced Search link (in blue letters) which always used to appear to the right of the Search button is gone. If I click Search again at this point I can see the Advanced Search link appear for a millisecond, but then disappear just as quickly. Also, if I refresh the page the same thing happens. I tried to duplicate this problem with Internment Explorer and it didn't occur, so it appears to be Firefox that is causing this issue. Of course when I contacted Ebay they told me my problem was that I wasn't using Internment Explorer! I love Firefox and do not want to switch!

You can try to clear the cache and cookies to see if that makes a difference:
<h3>Clearing Cache</h3>
#Go to Firefox > History > Clear recent history or (if no Firefox button is shown) go to Tools > Clear recent history.
#Under "Time range to clear", select "Everything".
#Now, click the arrow next to Details to toggle the Details list active.
#From the details list, check ''Cache'' and uncheck everything else.
#Now click the ''Clear now'' button.
<h3>Clearing Cookies</h3>
#Go to Firefox > Tools > Privacy > Remove Individual Cookies
#Find the site (ebay.com) that's having problems and clear all cookies.
#Restart Firefox
Further information can be found in the [[Clear your cache, history and other personal information in Firefox]] article.

How to add a new search criteria in Advance Search Page in OAF

HI,
In my application (R12) we can access customer related information from 2 places (2 different responsibilities as mentioned below), both are OAF pages.
1. AX receivables
2. Sales online
From both the responsibilities we can perform search for customer related information as well (Simple as well as Advance Search).
But Advance Search screen from 'Sales online' allows user to perform search, based on few additional fields as well such as 'Classification' (it's an lov based field).
Now, User is asking to add that field on search page of AX receivables as well.
So, how to add one more field (as search criteria), on an standard 'Customer' screen?
Additional Info :
1. LOV is based on HzPuiClassificationFilterVO
2. And this VO is available on both pages. (oracle.apps.ar.hz.components.search.server.HzPuiClassificationFilterVO)
So can we achieve this by Personalization only ? if yes plz share the steps as well.
Regards,
Adi

Yes. It is possible through personalization.
1. Create a criteria row under Advance Search
2. Create a Result Item under advance table columns
3. Create a Query Criteria Map based on the criteria and result item above.
Please note the newly added criteria field should be in the Searchresults VO attributes list.
Otherwise you need to extend the VO as well.
Hope this helps.
Regards,
-Mukesh.

Search Item drop-down does not show any data for Advanced Search.

Hi,
I have a requirement to add a new criteria to the existing Advanced Search region of 'My Employee Information' in Manager Self Service responsibility. I substituted the AdvancedSearchVO to include the new column. Using personalization i did the below steps to show the new column in the page,
1) Created a 'Message Styled Text' item under Table Layout region to display the result. I associated the View Instance (AdvancedSearchVO1) and View Attribute (AttrColumn).
2) In Advanced Search Panel created a new CriteriaRow and set the 'Search Allowed' property to True.
3) In Advanced Search Mappings i tried to create the new mapping but the Search Item drop-down does not show any of the CriteriaRow item. But Results Item shows the 'Message Styled Text' item created in step 1 above.
Any idea what i would be missing becasue of which 'Search Item' property does not show any data?
I am using OAF version 12.1.1.
Thanks, Suresh

Hi,
I faced the same situation but i still waiting for the solution.. this is my problem's thread..
Addition of LOV Search Filter using Personalization
But when i tried to create a new custom page with advanced table and created a new LOV column via personalization. i was able to create new search mapping.. but this is not happening in the seeded page case :(.
I m also looking for solution...if any one can provide some inputs on it , will be highly appreciated.
Thanks
Renu

Unable to create Table Bean advanced search criteria

Hi,
I want to create new search criteria for advanced search region. The reason being new search criteria i tried to add by personalization it didnt worked may be guessing construction mode is autocustomization mode. Somewhere i have seen if resultsbased it will work. Can someone confirm on this??
I'm trying to create new bean for search criteria at the specified location under <oa:table akRegionCode="EAM_AD_ASSET_RESULTS_TABLE" but unable to do so:
Here is the part of the page
<?xml version = '1.0' encoding = 'UTF-8'?>

<page xmlns="http://xmlns.oracle.com/jrad" xmlns:ui="http://xmlns.oracle.com/uix/ui" xmlns:oa="http://xmlns.oracle.com/oa" xmlns:user="http://xmlns.oracle.com/jrad/user" file-version="$Header: EAM_AD_ADVSEARCH_PAGE.xml 120.18.12010000.3 2009/02/11 09:21:55 smrsharm ship $" version="10.1.3_1147" xml:lang="en-US" xmlns:jrad="http://xmlns.oracle.com/jrad">
<content>
<oa:pageLayout id="EAM_AD_ADVSEARCH_PAGE" akRegionCode="EAM_AD_ADVSEARCH_PAGE" regionName="Asset Search" amDefName="oracle.apps.eam.asset.server.AdvSearchAM" controllerClass="oracle.apps.eam.asset.webui.AdvSearchPageCO" appMenu="EAM_MAIN_SS" amStateRequired="false" helpTarget="EAM_AD_ADVSEARCH_PAGE">
<ui:corporateBranding>
<oa:image id="corporateBranding" source="/OA_MEDIA/FNDSSCORP.gif" shortDesc="Oracle"/>
</ui:corporateBranding>
<ui:productBranding>
<oa:image id="productBranding" source="/OA_MEDIA/EAMBRAND.gif" shortDesc="Asset Management"/>
</ui:productBranding>
<ui:contents>
<oa:query id="EamAssetQueryRegion" mode="autoCustomizationCriteria" dispSimple="true" dispCustomized="true" dispAdvanced="true" defaultPanel="customized" controllerClass="oracle.apps.eam.asset.webui.AdvSearchSearchCO" simpleSearchPanelButtonLabel="Simple Search" viewConfPanelButtonLabel="Views" advSearchPanelButtonLabel="Advanced Search" customizePanelTitle="Views" saveSearchButtonText="Save Search">
<oa:simpleSearchPanel>
<oa:defaultSingleColumn id="AssetSimpleSearchRegion" headerDisabled="false" text="Simple Search">
<ui:contents>
<oa:messageTextInput readOnly="false" columns="25" prompt="Asset Number" rows="1" secret="false" maximumLength="30" shortDesc="Asset Serial Number" id="EamAssetNumber" promptTranslationExpansion="100%" user:akAttributeCode="EAM_ASSET_NUMBER" user:akAttributeApplicationId="426" required="no" selectiveSearchCriteria="true"/>
<oa:messageLovInput externalListOfValues="/oracle/apps/eam/lov/webui/EAM_ASSET_CATEGORY_LOV" readOnly="false" columns="25" prompt="Category" rows="1" secret="false" id="EamAssetCategory" promptTranslationExpansion="100%" user:akAttributeCode="EAM_ASSET_CATEGORY" user:akAttributeApplicationId="426" selectiveSearchCriteria="true" shortDesc="Category">
<lovMappings>
<lovMap criteriaFrom="EamAssetCategory" lovItem="EamAssetCategory" id="lovMap1"/>
<lovMap resultTo="EamAssetCategory" lovItem="EamAssetCategory" id="lovMap2"/>
<lovMap id="lovMap39" lovItem="EamAssetCategoryId" resultTo="EamAssetCategoryId"/>
</lovMappings>
</oa:messageLovInput>
<oa:messageChoice readOnly="false" prompt="Asset Route" pickListViewDef="oracle.apps.eam.asset.server.PicklistYesNoVO" pickListDispAttr="Meaning" pickListValAttr="LookupCode" id="EamNetworkAsset" promptTranslationExpansion="100%" user:akAttributeCode="EAM_NETWORK_ASSET" user:akAttributeApplicationId="426" shortDesc="Asset Route" allowBlankValue="false" defaultValue="N"/>
<oa:formValue id="EamAssetCategoryId" dataType="NUMBER"/>
</ui:contents>
</oa:defaultSingleColumn>
</oa:simpleSearchPanel>
<oa:simpleSearchMappings>
<oa:queryCriteriaMap id="AssetNumberMapSS" criteriaItem="EamAssetNumber" resultsItem="AssetNumber1"/>
<oa:queryCriteriaMap id="AssetCategoryMapSS" criteriaItem="EamAssetCategory" resultsItem="AssetCategory1"/>
<oa:queryCriteriaMap id="AssetRouteMapSS" criteriaItem="EamNetworkAsset" resultsItem="AssetRoute"/>
<oa:queryCriteriaMap id="AssetCategoryIdMapSS" criteriaItem="EamAssetCategoryId" resultsItem="AssetCategoryId"/>
</oa:simpleSearchMappings>
<ui:contents>
<oa:tableLayout akRegionCode="EAM_AD_ADVSEARCH_RESULTS" regionName="Results" controllerClass="oracle.apps.eam.asset.webui.AssetResultsCO" addChildren="true" id="EamResultsNr" user:akAttributeCode="EAM_RESULTS_NR" user:akAttributeApplicationId="426">
<ui:contents>
<oa:tableLayout id="ResultsTableLayout2" width="100%" rendered="true">
<ui:contents>
<oa:rowLayout id="RowLayoutRegion2">
<ui:contents>
<oa:cellFormat id="CellFormatRegion2">
<ui:contents>
<oa:switcher id="MappedTableRegion">
<ui:case name="ShowTable" id="ShowTable">
<oa:table akRegionCode="EAM_AD_ASSET_RESULTS_TABLE" regionName="Asset Search" blockSize="25" standalone="true" height="1" id="MappedTable" user:akAttributeCode="EAM_RESULTS_NR" user:akAttributeApplicationId="426" width="100%" rendered="true" userCustomizable="true" shortDesc="Mapped Table">
<ui:contents>
<oa:messageStyledText id="AssetNumber1" viewName="AdvSearchVO" viewAttr="InstanceNumber" shortDesc="Serial Number" prompt="Asset Number"/>
<oa:messageStyledText id="AssetDescription1" viewName="AdvSearchVO" viewAttr="DescriptiveText" shortDesc="Asset Description" prompt="Asset Description"/>
<oa:messageStyledText id="AssetCategory1" viewName="AdvSearchVO" viewAttr="AssetCategory" shortDesc="Asset Category" prompt="Asset Category"/>
I tried several ways :
OAPageLayoutBean pageLayout = oapagecontext.getPageLayoutBean();
OAQueryBean query=(OAQueryBean)pageLayout.findChildRecursive("EamAssetQueryRegion");
OATableBean oawebbeantb = (OATableBean)query.findChildRecursive("EAM_AD_ASSET_RESULTS_TABLE");
OAMessageLovInputBean ccidbean = (OAMessageLovInputBean)oapagecontext.getWebBeanFactory().createWebBean(oapagecontext, OAWebBeanConstants.LOV_TEXT, null, "xxValidation");
if (oawebbeantb==null){
throw new OAException("Error this is a test!", OAException.ERROR);
oawebbeantb.addIndexedChild(ccidbean); --here it getting null
OR
OATableBean oawebbeantb = (OATableBean)oawebbean.findIndexedChildRecursive("EAM_AD_ASSET_RESULTS_TABLE");
OAMessageLovInputBean ccidbean = (OAMessageLovInputBean)oapagecontext.getWebBeanFactory().createWebBean(oapagecontext, OAWebBeanConstants.LOV_TEXT, null, "xxValidation");
oawebbeantb.addIndexedChild(ccidbean); --here it getting null
Please someone help me on this..
thanks,
mallik

1) Search panel textinput item should be search allowed true and prompt is need. no other property need to set.
HERE YOU DONT WANT TO SET VIEW INSTANCE AND ATTRIBUTE SINCE WE ARE DOING FOR EXTENDED VO ITEM AS SEARCH ITEM.THAT'S OK. I TRIED WITH YOUR COMMENTS FOR TEXTINPUT ITEM TOO.
Comment--
textinput item created is a simple item without any VO instance , etc.
There is no question of extended VO item, its a simple textinput item.
value in this field is going to compare with the values in result table.
2) Search mapping, only search item id and result item id need to set.
I'M DOING HERE MAPPING FOR ABOVE SEARCH ITEM ID AND RESULT ITEM ID
Comment-- Perfect !!
3) Item created in table , after you extended Vo, view instance and attribute needs to set.
WHERE DO YOU WANT THIS TO BE SET?? CAN YOU ELABORATE THIS MORE PLEASE.MAY BE I'M MISSING HERE SOMETHING.
Comment-- you must have created message styled text item in adv table bean, assign VO instance and attribute to it, right?
4) One more thing Parag, do i need to include where clause for extended VO item in view object??
for ex:
where attribute(this is extended vo item)=:4
Comment-- No need. this will be handled by point#2 above, i.e. criteria and result items.
--Parag Narkhede

OAF Page Personalize Page to add a new criteria in Advance Search

Hi All,
I am new to OAF. I need to add a new criteria (Asset Activity) to the Work Order Advance Search page in EAM module.Asset activity field has to pick from the 'Create Work Order' Form. I can able to identify the CO class associated with this field in the 'Create Work Order' form.
How to achieve this by personalizing the Work Order Advance Search Page.
Any help would be much appreciated.
Thanks in advance,
-Mukesh.
Edited by: Mukesh on May 1, 2012 12:48 PM

Hi All,
I have done the following steps.
1. From the Work Order Advanced Search Page, clicked on Personalize "Advanced Search".
2. Created a Criteria Item with ID 'AssetActivityAS' and also created a Message Styled Text under this criteria.
3. Back to the Advanced Search Page, clicked on 'Personalize Page' page in the bottom.
4. Create an Advanced Search Mappings with ID 'AssetActivityMap' and Results Item as 'WorkOrdersVO.AssetActivity' and Search Item as 'AssetActivityAS'.
5. But when I click on Apply, it's throwing the following error.
oracle.apps.fnd.framework.OAException: oracle.adf.mds.exception.MDSRuntimeException: Unable to find component with absolute reference = /oracle/apps/eam/workorder/webui/EAM_EW_START_PAGE.WorkOrdersVO.AssetActivity, XML Path = null. Please verify that the reference is valid and the definition of the component exists either on the File System or in the MDS Repository.
at oracle.apps.fnd.framework.OAException.wrapperException(OAException.java(Compiled Code))
at oracle.apps.fnd.framework.webui.OAWebBeanHelper.processRequest(OAWebBeanHelper.java(Compiled Code))
etc...........
I found WorkOrdersVO(oracle.apps.eam.workorder.server.WorkOrdersVO) from Business Component References Details of About Page: Work Orders.
Am I doing the right steps to add a new search criteria in Advance Search page?
Can anyone help me to resolve this issue?
Thanks in Advance,
-Mukesh

Problem in using quick and advanced search based on transient items

Hi everybody
I want to have an unbound string item in my form and allow users to use advanced search and quick search on that item.
I read the following post About advanced search and added a transient
item on view object and overrode the advance search method in application module and realized that the value of that string was
added to arguments.
Then I decided to add this transient item on entity object instead of view object so that we were able to add the item in one place and
use it in several view objects. I added an item in the entity and unchecked the persistent flag but I can't set queryable flag since it was disable.
I added the item in the view object and by use of application definition I forced the item to be shown in the advance search.
I generate the application and the item was shown correctly in the advanced search but when I set the item in advanced search its value
was not sent to advance search method.
Is it a bug ? (value of the field in the advanced search section was not sent to advanced search method )
Is it a way to add a queryable transient item in the entity object and still benefit from overriding advanced search method ?
I am using Jdeveloper 10.1.3 and Jheadstart 10.1.3.
Any help would be appreciated.
Best Regards
Navid

Navid,
JHeadstart checks whether the attribute definition is queryable before adding it to the list of advanced search attributes. A transient VO attribute can still be set to queryable, for a transient EO attribute this is not possible. We will remove this check on queryability in the upcoming patch release, since you have a valid use case. For now, you can subclass JhsSearchBean and override method createArgumentListForAdvancedSearch and comment out the check for "def.isQueryable()".
Steven Davelaar,
JHeadstart Team.

Query bind parameter in Advanced Search

Hi,
We are using a query bind parameter in an Advanced Search . The parm that is passed is on an Lov field which works when we use the lov to populate the field but doesn't get passed if we enter the value manually instead.We are using the setActionListener tag in a copy of the findLovItem.vm file:
<af:setActionListener from="#{searchxxxx.criteria.xxxx+attributename+}"
to="#{QueryBindParamBean.+attributename+}"
The 'from' value is taken from the 'value' field in SelectInputText tag of that attribute ('+attributename+') found in the Advanced_Search_Lov_Item in the .jspx. We are doing the exact same thing in a form view (not the search) for the same attributes but are using the corresponding value for that attribute instead and it works no problem:
<af:setActionListener from="#{xxxx+attributename+LovItem.lovFieldValue}"
to="#{QueryBindParamBean.+attributename+}"
any ideas why the value isn't being passed in the search page when entered manually?
thanks!

Hi,
It does not directly ring a bell for me why you cannot copy this value. But since JHeadstart is simply using a bean with a Map to store it's values, it does not sound like a JHeadstart issue per se.
To simplify the test case, you could create a simple drag-and-drop ADF application without JHeadstart and see if the same problem occurs there. If so, can you please log a TAR at MetaLink ( http://metalink.oracle.com/ ), or ask this question at the JDeveloper forum? Thanks.
Evert-Jan de Bruin
JHeadstart Team

LOV Validation in Advanced Search

Similar Messages

Maybe you are looking for