While giving add fields in advanced mode

Hai everyone, i met with a problem such that while using search in advanced mode we can add fields multiple times. Can anyone suggest me to restrict same field appearing more than one time in advanced mode --> add fields.
Thanks in advance.

Hi,
there is no such restriction as far as I know. Background is that you may want to define "OR" condition for a field
Frank

Similar Messages

  • In Matrix Value is duplicating while giving add row

    In matrix i have given add row but the value is duplicating from the previous row in update mode.in add mode its ok
    and while clicking update =    error is coming "This entry already exists in the following tables "
    plz help
    its Urgent

    Hi Nikhil k,
    This is a kind of behavior of matrix.
    So what you can do is that after calling the AddRow () Method put the blank values in the newly added row. Use this as follows:
    oMatrix.AddRow();
    oMatrix.FlushToDataSource();
    this.oForm.DataSources.DBDataSources.Item("@DETAILTABLE").SetValue("U_Code", oMatrix.VisualRowCount - 1, "");
                                                this.oForm.DataSources.DBDataSources.Item("@DETAILTABLE").SetValue("U_Name", oMatrix.VisualRowCount - 1, "");
    oMatrix.LoadFromDataSource();
    Hope it helps.
    Thanks & Regards
    Ankit Chauhan

  • How to control attributes in 'Add Fields' in af:query Advance mode

    Hi,
    The VO attributes those set Queriable=false doesn't appear in the Add Fields dropdown in ad:query advance mode.
    But I have few attributes in a VO those required to use in VO query so I cannot set those attrbutes Queriable as false.
    Also observed that QBE doesn't work for the attributes whose Queriable set as false.
    So can someone please suggest me how to achieve below,
    VO attribute which having Queriable=true but doesn't appear in 'Add Fields' dropdown in af:query advance mode.
    JDeveloper version 11.1.1.7.0
    Edited by: user12820425 on Mar 21, 2013 10:16 AM

    Hi Naresh
    Thanks for your reply.
    In ViewCriteria -> UI Hints we can set attribute Rendered Mode as never, but that perticular attribute still appear in 'Add Fields' section.
    I think renderedMode=never means that attribute doesn't appear in Advance or Basic mode user need to manually select that attribute.
    So please suggest me how to achive my requirement.

  • Bug after adding fields in advanced search mode of af:query

    We are migrating from JDeveloper 11.1.1.6 to 11.1.1.7.
    I noticed the following issue:
    In a page with search criteria (based on a view object), when the user adds an additional field in advanced search mode and clicks on a full submit button in the page, the following browser popup appears:
    "This page is asking you to confirm that you want to leave - data you have entered may not be saved."
    This was logged as a bug in Oracle Support but we have not been able to find a workaround yet.
    This is the only issue currently blocking us from migrating to 11.1.1.7. Has anyone else faced this issue? Any ideas on how we can bypass this behavior?
    Thank you,
    Gabriel.

    Unfortunately, the latest update from Oracle Support was that they no longer consider this a bug!
    SR 3-7706485141: Additional Fields in af:query problem - JDeveloper 11.1.1.7
    Bug 17346704 - ADDING FIELD TO AF:QUERY ADVANCED SEARCH CAUSES SPURIOUS WARNING DIALOG POPUP
    1. I cannot understand how something that blocks user actions and cannot be bypassed in any way could be considered "acceptable behavior".
    2. I also do not understand how a Bug can be lodged and then have its status changed to "Not a Bug".
    3. Even if we were to ignore this issue and convince our customers that they should be delayed by meaningless popups while working (which we cannot), their is still another issue that makes this functionality dysfunctional. When the user clicks on "Stay on Page" the popup closes and the page freezes and becomes unresponsive.
    Off course this is another issue and a different SR should open, but I think it shows that something is going very wrong with this functionality.
    I wonder if anyone else is considering using JDeveloper 11.1.1.7.0 in a production system.

  • How to control the number of fields in the Advanced mode in af:query

    Hi,
    How to control the number of fields in the Advanced mode in <af:query>?
    Say i have 20 fields in my table and i created a view criteria with 2 fields. It would work perfectly in Basic mode. But in the Advanced mode all other fields selection is possible on clicking the ADD Fields button. I did not want the client to make a search with all 20 fields. Only 10 fields are to be listed in the Advanced Mode even though there are 20 fields in my table.
    How do i control the list of fields in ADDFields button?
    Any ideas?
    KR

    You can uncheck the Querable property of the attributes which you need not show up in the Advanced Mode (but they will not show up in other modes too !) or programatically set the same as mentioned here -
    http://adfcodebits.blogspot.com/2010/11/bit-27-setting-view-object-attributes.htmlAlso you can hide the AddFields button as suggested here - http://www.notjustjava.com/2011/12/cool-tips-to-showhide-components-of-the-query-control-of-adf/

  • Controlling criteria in Advanced Search 'Add Fields'

    Hi all,
    Jdev Version: Studio Edition Version 11.1.1.7.0
    Background
    I have two VOs described as below -
    TaskVO - Fetches a list of tasks
    TaskUserVO - Fetches the list of users of tasks - Users may be assignees or owners identified by value in column 'USER_SOURCE_TYPE'.
    A view link relates TaskVO & TaskUserVO by the TASK_ID (primary key of TaskVO).
    I have a view criteria for displaying a search by assignee and search by owner as criteria in my search query region. For this, I have used 2 inline view criteria in my view criteria defined in TaskVO. Both inline view criteria are on TaskUserVO (one for Owner & other for Assignee) and each takes 2 bind variables -
    i. USER_SOURCE_TYPE - This can either be ASSIGNEE or OWNER
    ii. NAME - This is the name of the assignee or owner.
    Issue Description
    The issue I face is in Advanced Search - Add fields. Since the same inline view criteria (TaskUserVO) is added twice (once for Owner & other for Assignee), the Add fields shows 'Name' twice in the list.
    I need to show the Add field label name as 'Assignee' corresponding to the Assignee inline VC and name as 'Owner' for Owner inline VC. How can I achieve this?
    In general, I am also looking for ways to pro-grammatically modify the 'Add field' list (I understand that the Queriable flag controls this list declaratively). Any suggestions on this?
    Could QueryModel/QueryDescriptor help in achieving this?
    Thanks,
    Srini

    Any thoughts on this one?

  • How to maintain the Goods reciepent field in edit mode while SHC creation

    Hi Experts,
    Can any one suggest me a solution, this is the requirement in SRM 5.0 version classic.
    Business wants to keep the Goods recipent field in edit mode instead of in grey mode, so that User can edit and assign someone at the time of creation of shopping cart.
    This is because If i raise a shopping cart i will be goods recpient by default, but business does not want that they want to edit  and assign a person at the time of creation of shopping cart .
    Can it be possible in the standard template.
    If so what has to be done. Please suggest !!!
    Regards
    Srujan.K

    Hi
    Srujan:- while creating a cart you might get a list of good recipient right so you can assign whoever you wish to be a good recipient right. while creatiing a cart good recipient was determined and partner functions are created for good recipient. do you want to edit them again.
    Can we change Goods Recipient after shopping cart is ordered
    nagaraj:- in old srm it helps but srm 550 say no
    http://help.sap.com/saphelp_srm50/helpdata/en/84/a7e3389870c05ce10000000a114084/content.htm
    we can not make default good recipient
    for eg srujan create a cart by default naga become a good recipient . that is old. this requester attribute dont work for dual purpose.
    it uses sfor only on behalf of only
    br
    muthu

  • AF:Query -how to hide attribute in basic mode but show/add in advanced mode

    Hello,
    I have a requirement to initially hide some attributes when displayed in BASIC mode of af:query with the possibility to add these hidden attributes in ADVANCED mode.
    Is it doable somehow?
    edit: JDeveloper 11.1.2.3.0, ADF BC
    Regards,
    Miroslaw
    Edited by: Miroslaw on 2013-01-16 14:59

    Hi,
    Always mention your JDev version.
    If you are using BC4J as your model, you can create view criteria and set which attribute to be visible in which mode under UI hints, and use this criteria as query panel in your page.
    -Arun

  • [svn:fx-4.0.0] 13428: Add mask and advanced blend mode support to SpriteVisualElement

    Revision: 13428
    Revision: 13428
    Author:   [email protected]
    Date:     2010-01-11 15:16:16 -0800 (Mon, 11 Jan 2010)
    Log Message:
    Add mask and advanced blend mode support to SpriteVisualElement
    SDK-24949 - Can't apply hue blend mode to FXG instance
    Copied blendMode and mask logic from GroupBase.
    QE notes: Add tests to SVE
    Doc notes: Update docs to mention mask and blendMode support
    Bugs: SDK-24949
    Reviewer: Pete, Ryan
    Tests run: checkintests, FXG
    Is noteworthy for integration: Yes
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-24949
        http://bugs.adobe.com/jira/browse/SDK-24949
    Modified Paths:
        flex/sdk/branches/4.0.0/frameworks/projects/spark/src/spark/core/SpriteVisualElement.as

    Hi Mathais,
    I assume you have installed the OPC enum services in the same machine where xMII UDS is running.
    Also make sure that the browsing mode is set to true in the OPC Server.
    We had the same issue...and were receiving the same error...but once we changed teh Browing mode at teh OPC server to true, tag quesries started working....
    Hope it helps...
    Pramod

  • Can we add fields from structure while enhancing datasource

    Hello all,
    I am trying to enhance a SAP delivered datasource. Is it possible to add fields from a logical database structure or do we have to add fields only from a table.
    Is the procedure the same.
    Thanks a lot

    hi KM,
    you want to drop all the added fields or some ?
    go to the extract structure screen,
    rsa2->type in your datasource name, double click the
    extraction structure, to delete some fields, click append structure, in next screen mark the fields and sign '-'.
    to delete the append structure, check this
    How to delete append structure
    Delete append structure with a long name
    hope this helps.

  • Duplication of attributes in Add Fields dropdown of  Advanced Search

    I am instantiating a secondary VO twice in the View Criteria. This leads to a duplication of query able attributes in the Add Fields drop down.
    Is it possible to override certain method in af:query, and suppress the attributes appearing in the Add Fields drop down.

    Unchecking the queryable attribute would remove the attributes from the Add Fields drop down all together. I need to avoid duplication and display the attributes only once.

  • Making short text field in Display mode for one particular Purchasing

    Hi All,
    This is regarding Making the Short text field in Display mode of PR for one Particular Purchasing.. i am giving you a bit elaborate...We are into E-Catalog Procurement.I will do the shopping from the Vendors external catalog and i will return back to SAP.
    While doing so, i dont want the user to change the Short Text field. I want that field shud display the Description. When i tried with the Screen Layout settings, it is fully grayed out and i am not able to see the Description of the Material. Is there any other options to get this enabled?. Please advice me on this settings to be done. Thanks in Advance.
    With Regards,
    Saakithyan

    Hi
    Define a Field selection key (new not the one which is assigned to document type) which makes  short text editable in screen layout config. and assign it to functional authorization value in t.code OMET. (it should be numeric). Then assign that functional authorization value in user master SU01 for users with parameter id EFB.
    Then it will work
    Regards
    Antony

  • While adding custom field in urgent change-Create new field button in AET is not coming

    Dear All,
    we have requirement to add some custom fields in urgent change document. while adding custom fields using AET, create new field button is not coming.
    Thanks in advance. points will be awarded.
    Rahul

    Hi Jignesh,
    Thanks for your valueble inputs, it really helped me to understand the process.
    I checked in Web UI configuration for urgent change document as you mentioned but still that button is not coming.
    In transaction BSP_WD_CMPWB, i have created enh. set: Z_ENHANCEMENT_SET.
    Can you tell what to selelect in application and page popup which comes after selecting Enhance component button. Actually i tried but i am not able to add new record in conf.
    Thanks in advance.

  • af:query   component  "Add Fields"  clarification

    Hi, in the advanced mode of <af:query> using the "Add Fields " function , duplicate fields(same search field can be added multiple times) can be added. Is this a bug or a feature. Where can i refer the doc to confirm this . Thanks.

    I don't know that the documentation specifically says anything about this. [url http://download.oracle.com/docs/cd/E14571_01/web.1111/b31973/af_query.htm#BGBCHFEF]here is one piece of documentation.

  • Af:query 'Hiding Unwanted Operators in Advanced mode having blank selection

    Hi,
    This is regarding 'Hiding Unwanted Operators in Advanced mode of af:query Component', I have followed the post by Jobinesh (http://jobinesh.blogspot.com/2013/01/prart-2-hiding-unwanted-operators-in.html)
    The attribute is non-default attribute and when we add the attribute from 'Add Fields' section it will be having blank selection option even if I have added below two lines under 'ViewAttribute' tag.
    <CompOper Name="Name" ToDo="-1" Oper="ISBLANK" MinCardinality="0" MaxCardinality="0"/>
    <CompOper Name="Name" ToDo="-1" Oper="" MinCardinality="0" MaxCardinality="0"/>
    Kindly suggest:
    1. How to remove blank selection operator.
    2. How to set particular operator as default operator in XML.

Maybe you are looking for