Hide the expand button if count of data is less than 10

 I have the following requirement. The user wants to hide the expand button on the row grouping and only shows the subtotal when the underlying data count is less than 10
e.g. if in the two years range, the count of records is less than 10, hide the expand button for NewYork Office and disallow users drill down to year and month
Perry Zhou
SharePoint; TFS; SSIS SSAS SSRS
blog
email linkedin

Hi Perry,
As far as I know, OOB it's not possible, so you have to rely on some javascript code to do the same for you. You can use JSOM or REST api to get the count of items in list and then use jquery to show/hide the expand/collapse button and remove the onclick
event of Group Name.
Hope it will solve your problem.
Best Regards,
Brij K
http://bloggerbrij.blogspot.co.uk/

Similar Messages

  • HOWTO: Hide the delete button in a NavigatorBar

    HOWTO: Hide the delete button in a NavigatorBar (JSP)
    Goal: Hide the delete button in a NavigatorBar or JSNavigatorBar Data Web Bean. This example works for either bean.
    Solution: Edit the .jsp file containing your NavigatorBar bean. For a generated BC4J JSP application, the file is YourView_Top.jsp.
    Find the code that instantiates the NavigatorBar. It will look something like:
    <jsp:useBean class="oracle.jbo.html.databeans.NavigatorBar" id="tb" scope="request">
    <%
    tb.initialize(pageContext, "MyProject1_bizcomp_BizcompModule.MyView");At this point, add the following line of code to hide the delete button:
    tb.getButton(tb.NAVIGATE_DELETE).setButtonVisible(false);You can find the variable names for the other navigator buttons in the javadoc for oracle.jbo.html.databeans.BaseNavigatorBar. In the online help, this is under Reference -> Business Components Reference.
    null

    Georges,
    This has come up before, and after some experimentation, there's not a straightforward way to do it.
    There are two possible solutions that I can think of:
    1. Write your own custom bean and/or extend the beans provided to modify them to your needs.
    2. Wait for the 3.2 release at the end of the month. This release provides custom data tags with much finer grained control over specific items such as the buttons.
    I think 2 is preferable, if you have the time to wait.

  • Hide the Save button in tool bar in pdf form

    Hi All,
    I need to hide the save button in the tool bar in pdf form out put. I need not hide the print button, hand tool and etc.
    I have seen some forum threads,but i am not able to get the answer.
    I have refered this links
    http://help.sap.com/saphelp_nw04/helpdata/en/e1/fd9841e2ebb05fe10000000a1550b0/frameset.htm
    How to hide tool bar from Adobe Form
    The above link contains some scripts,The code id used for hide the hole tool bar not only save button.
    I need to hide only save button in the tool bar.
    How to hide the save button in the tool bar ?
    Thanks and regards,
    Boopathi M

    Adobe Designer 7.1 uses XFA 2.4
    If you can upgrade to Adobe desinger 8.2 to be abel to use XFA 2.8 you can code in the following way:
    Write the following code in the preSave method
    if (do_not_save_condition == 1) then
      xfa.event.cancelAction = 1
    endif
    Adobe Quote
    cancelAction specifies whether to cancel a forthcoming action.
    This property applies only to the following scripting events: prePrint, preSubmit, preExecute, preOpen, and preSign.
    The user experience is determined by the scripting event that contains the cancelAction reference:
    u2022  preOpen - The drop-down list does not expand to display the list of values. 
    u2022  preSubmit - Form submission does not occur. 
    u2022  preSign - The form is not digitally signed. 
    u2022  prePrint - No print dialog boxappears, and the form is not printed. 
    u2022  preSave The form is not saved. The user experience is that no action occurred. 
    Edited by: Reema Shahbazkar on Sep 10, 2008 7:54 PM
    Using this, the save button will still be visible but, you can prevent the form from being saved.

  • How to hide the "EXIT" button on the ESS Personal inf. iViews

    Hello,
        We are using SAP ECC 6.0 + SAP EP 7.0 + ESS 1.0 (latest Releases).
        In the ESS iViews (Java WD) for Personal information (Adresse, Bank, Family, etc. there is the Button "Exit"..
      Does any have any Idea where and how to hide this "Exit" Button in the iView/Java-WD?
    Many Thanks,
    Nazih

    Hi Chris,
      thanks for your reply.
      If you mean to hide the button using the iView/WD Personalisation by rightclick on the iView in PCD and then Review, well yes i know this and i have tried this already before and we were able to hide some not required input fields in the Webdynpro, but we were not able to find and to hide the "EXIT" Button using the personalisation..!!?? you know why?
    Why to hide the Exit button, i will tell you why, in the iView for maintainig the ESS Personal Information -> e.g. Adresse --> Edit Adresse View (Roadmap view No. 2) --> when User click on the Exit Button --> This will open new browser Window with ESS... ---> This second Browser Window (Pop up) would confuse the User, since he already have an opened window, so the Customer mean why open new window, since the user can simply click the Button Back and so his data are also saved..
    How can we manage to control the behaviour of the Button, so the iView is closed safety without that new Pop-up windows are opened...
    Many Thanks,
    Nazih

  • Hide the Execute Button

    Dear all,
    Im writing a report for reading details from a barcode reader.
    My requirement is in At seletion screen I do the necessary processing and want to hide the execute button.
    Please could any one help me.
    Thanks
    ann

    Hi Ann:
    It's late for my answer, but I send this post. May be useful.
    I faced the same problem for other reasons.
    I solved the problem by doing:
    AT SELECTION-SCREEN OUTPUT.
      DATA gt_ucomm TYPE TABLE OF sy-ucomm.
      APPEND: 'ONLI' TO gt_ucomm.
      CALL FUNCTION 'RS_SET_SELSCREEN_STATUS'
           EXPORTING
                p_status  = sy-pfkey
           TABLES
                p_exclude = gt_ucomm.
    This works well if your selection screen is number 1000 (default).
    But if you define a selection selection screen with another number, like this:
    SELECTION-SCREEN BEGIN OF SCREEN 100.
    PARAMETERS:
        p_examle like sy-datum.
    SELECTION-SCREEN BEGIN OF SCREEN 100.
    And you don't define a Status GUI for screen 100, then the solution does not work because sy-pfkey is not informed.
    Then I solved by changing the call to the Function Module in this way:
    AT SELECTION-SCREEN OUTPUT.
      DATA gt_ucomm TYPE TABLE OF sy-ucomm.
      APPEND: 'ONLI' TO gt_ucomm.
      CALL FUNCTION 'RS_SET_SELSCREEN_STATUS'
           EXPORTING
                p_status  = '%_00'  "Status GUI for screen 1000
           TABLES
                p_exclude = gt_ucomm.

  • Hide the DELETE button in EditCurrentRecord !!!

    Hi,
    Who can tell me how can I hide the DELETE button of the EditCurrentRecord ?
    Thank You !

    Georges,
    This has come up before, and after some experimentation, there's not a straightforward way to do it.
    There are two possible solutions that I can think of:
    1. Write your own custom bean and/or extend the beans provided to modify them to your needs.
    2. Wait for the 3.2 release at the end of the month. This release provides custom data tags with much finer grained control over specific items such as the buttons.
    I think 2 is preferable, if you have the time to wait.

  • Disable/Hide the Refresh Button in Child report

    Hi All,
    Our Environment is BOXI-R2;
    We have a Master Report calling a Child Report (based on Open Document);
    Our requirement is to hide the" Refresh Button "in the child report Layout
    we tried using "hideRefresh=true"
    but the child report is not responding to the above clause
    Help us in this,
    if this is a BUG in XI R2, let us know the Service Pack details
    Thanks

    Joe , Thanks for your Inputs..
    our master report has the aggregated Measure , when the user clicks on this , it has to open a child report (with paramters from master report).
    We are aware of customizing "viewer.js " file (under BO install home) with "refreshDocIcon = null".
    But is this the only solution to hide the refresh button in the child report ?
    SInce its already a PRODUCTION environment, our customer won't allow to change the standard settings of the product.
    Thanks

  • Hide the submit button programatically

    Hi Friends,
    i have standard page , in that, submit button is rendering programatically,i want to hide that submit button. do i need to extend standard controller to hide the submit button? here below code i have to hide the Activate button. can any one give guide to achive this solution.
    standard controller process request code....
    public void processRequest(OAPageContext oapagecontext, OAWebBean oawebbean)
    super.processRequest(oapagecontext, oawebbean);
    NegotiationCreationAM negotiationcreationam = (NegotiationCreationAM)oapagecontext.getApplicationModule(oawebbean);
    String s = getCurrentStepCode(oapagecontext, oawebbean);
    if(oapagecontext.isLoggingEnabled(1))
    oapagecontext.writeDiagnostics(getClass().getName() + ".processRequest ", " currentStepCode " + s, 1);
    mIsReviewPage = "Review".equals(s);
    mIsItemDetailPage = "ItemDetail".equals(s);
    mIsHeaderPage = "Header".equals(s);
    mIsViewNetChangesPage = "ViewNetChanges".equals(s);
    mIsUpdatePfValuesPage = "UpdatePfValues".equals(s);
    if(!negotiationcreationam.isTemplate() || negotiationcreationam.isTemplate() && !mIsReviewPage)
    OAWebBean oawebbean1 = oawebbean.findChildRecursive("SaveTemplateBtn");
    oawebbean1.setRendered(false);
    OAWebBean oawebbean8 = oawebbean.findChildRecursive("Activate");
    oawebbean8.setRendered(false);
    if(negotiationcreationam.isTemplate())
    OAWebBean oawebbean2 = oawebbean.findChildRecursive("SaveBtn");
    oawebbean2.setRendered(false);
    if(mIsReviewPage)
    OASubmitButtonBean oasubmitbuttonbean = (OASubmitButtonBean)oawebbean.findChildRecursive("Activate");
    oasubmitbuttonbean.setRendered(true);
    String s1 = null;
    if("ACTIVE".equals(negotiationcreationam.getTemplateStatus()))
    s1 = oapagecontext.getMessage("PON", "PON_TEMP_INACTIVATE", null);
    else
    s1 = oapagecontext.getMessage("PON", "PON_TEMP_ACTIVATE", null);
    oasubmitbuttonbean.setLabel(s1);
    oasubmitbuttonbean.setText(s1);
    if(!mIsHeaderPage || negotiationcreationam.isTemplate())
    OAWebBean oawebbean3 = oawebbean.findChildRecursive("ApplyTemplateBtn");
    oawebbean3.setRendered(false);
    if(!mIsUpdatePfValuesPage)
    OAWebBean oawebbean4 = oawebbean.findChildRecursive("ApplyPfValuesBtn");
    oawebbean4.setRendered(false);
    if(mIsReviewPage)
    setPageBtnsForReviewPage(oapagecontext, oawebbean);
    if(!negotiationcreationam.isTemplate())
    setEditButtons(oapagecontext, oawebbean);
    if(negotiationcreationam.isAmendment() || negotiationcreationam.isMultiRoundDocument())
    OAWebBean oawebbean5 = oawebbean.findChildRecursive("ReviewChangesBtn");
    oawebbean5.setRendered(true);
    if(mIsViewNetChangesPage)
    setPageBtnsForReviewPage(oapagecontext, oawebbean);
    OAWebBean oawebbean6 = oawebbean.findChildRecursive("EditBtn");
    oawebbean6.setRendered(mDocIsEditable);
    OAWebBean oawebbean9 = oawebbean.findChildRecursive("ViewDocumentBtn");
    oawebbean9.setRendered(true);
    OAWebBean oawebbean7 = oawebbean.findChildRecursive("OkBtn");
    oawebbean7.setRendered(mIsItemDetailPage);
    OAWebBean oawebbean10 = oawebbean.findChildRecursive("ReviewBtn");
    oawebbean10.setRendered(!mIsItemDetailPage && !mIsUpdatePfValuesPage && !mIsReviewPage && !mIsViewNetChangesPage);
    if(!mIsItemDetailPage && !mIsUpdatePfValuesPage && !mIsReviewPage && !mIsViewNetChangesPage)
    addSideBar(oapagecontext, s, negotiationcreationam.isTemplate());
    private void setEditButtons(OAPageContext oapagecontext, OAWebBean oawebbean)
    if(oapagecontext.isLoggingEnabled(1))
    oapagecontext.writeDiagnostics(getClass().getName() + ".setEditButtons ", " mDocIsEditable " + mDocIsEditable, 1);
    if(!mDocIsEditable)
    OAWebBean oawebbean1 = oapagecontext.getPageLayoutBean().findChildRecursive("HeaderEditButton");
    oawebbean1.setRendered(false);
    oawebbean1 = oapagecontext.getPageLayoutBean().findChildRecursive("ItemsEditButton");
    oawebbean1.setRendered(false);
    oawebbean1 = oapagecontext.getPageLayoutBean().findChildRecursive("ControlsEditButton");
    oawebbean1.setRendered(false);
    oawebbean1 = oapagecontext.getPageLayoutBean().findChildRecursive("ContractsEditButton");
    if(oawebbean1 != null)
    oawebbean1.setRendered(false);
    oawebbean1 = oapagecontext.getPageLayoutBean().findChildRecursive("SuppliersEditButton");
    oawebbean1.setRendered(false);
    Thanks in advance,
    vamshi

    Vamshi,
    Extending CO would anyways be required in either of the approach. Now let me brief you which approach you can use :
    1) If you need to hide the submit button while rendering of page, based on some logic, you can ahead with your approach extending the CO and in process request get refrence of submitbutton bean and use API, setRendered(false);
    2) If this button needs to be hidden on some logic on a post event on the page i.e. in process form request, its better to have a tranient attribute and a PVO approach u worked on tutorial.
    Apprach 1 can be used in case 2 also but in that case you would have do an extra looping on the page, by redirecting to same page retaining the AM. I hope this helps up to decide the approach.
    --Mukul                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • Hide the Approve button in TRIP transaction

    Please,
    I read that I if I want to hide the 'Approve' button automatically I must pass proper values in Auth Object F_TRAVL and P_TRAVL.
    Do you know, specifically, which authorization field and value I must have in P_TRAVL?
    I thank you in advance,
    Cláudia.
    Edited by: User BasisMasterUser on Mar 30, 2011 7:56 PM
    Edited by: User BasisMasterUser on Mar 30, 2011 7:57 PM

    Hi and thanks for the answer.
    We use the transaction PRAP for approval all the travel, so we need to prevent a simple user can approve the trip in the TRIP transaction. As I could not find an authorization object that correspond to the button of approval, we thought better to hide it.
    Unfortunately I did not see in the TRVPA feature anything that influences me in the way of approval, except that the WRP is equal to 3 which sets the approval status only for travel completed.
    Am I mistaken?
    I thank you again,
    Cláudia.
    Edited by: User BasisMasterUser on Mar 31, 2011 3:35 PM

  • How do I hide the admin button after someone has logged in as the administrator?

    Hi everyone,
    I am using Dreamweaver CS3, my question is:
    I have a login page that has check boxes at the bottom of the page that tell the database whether the user is an administrator or not.
    After the owner of the site has logged in as the administrator I would like to be able to hide the administrator button, can this be done with PHP, if so how do I do it?
    Thanks.

    Hello,
      Please try this:
    <?php
        function loggedin(){
            return isset( $_SESSION['loggedin'] );
        function require_login(){
            if( !loggedin() ){
                    header( 'Location: /login.php?referrer='.$_SERVER['REQUEST_URI'] );
                    exit;
    ?>
    Good Luck!
    Sean Colicchio
    Server Engineer
    hosting.com

  • HT1351 I'm trying to manually sync all my music to my iPod touch, but whenever I click the sync button it counts to 5 then stops. Is this because I have to check all 3055 songs individually? If so then I'm quitting with apple as a whole....

    I'm trying to manually sync all my music to my iPod touch, but whenever I click the sync button it counts to 5 then stops. Is this because I have to check all 3055 songs individually? If so then I'm quitting with apple as a whole....

    Sync and manually manage are two entirely different things.  You either sync or manually manage.
    Manually manage is drag and drop.
    Sync is when you select what you want and then sync.

  • Hide the Email Button

    Hi,
    Is it possible to hide the email button when it is clicked and have it replaced with a comment of some type, ie 'Thank you for your submission!'
    Frank

    This is what I don so far.
    I created the Submit by Email button and made the presence invisible. then I created another button (button1) and the control type is regular (not execute or submit)I then added the script
    EmailSubmitButton1.execEvent("click");
    Button1.presence="invisible";
    app.alert("Thank You for Your Response");
    to the Click option in the javascript window. Should one button be over the other button and how do I click the button to ignitate the emailing process. Nothing happens. I appreciate you help;
    Frank

  • HT1040 trying to make an ibook and have 800 photos, want format of 8 photos/page, but default is not that- "create" the initial book from iphoto "album" it loads less than 800 pics and then when i change layout i have blanks.

    trying to make an ibook and have 800 photos, want format of 8 photos/page, but default is not that- "create" the initial book from iphoto "album" it loads less than 800 pics and then when i change layout i have blanks.
    if i clear the book so that it is all blanks and then try to load in the pictures i have it loses the chronology of the pictures that i had established in the album.
    is there a way to import photos into an ibook template and keep the original order of the photos without having to do them one at a time?
    also, is there a way to insert a photo rather than just dragging it? i have tried the cut and paste funciton but it doesn't seem to work, the target site doesn't seem to register with iphoto.
    many thanks for your help.

    Photos are added to book in chronological order.  So if you want to add them to a book in the order you have placed them manually in an album do the following:
    1 - select all the photos in the album.
    2 - use the Photos ➙ Batch Change ➙ Date menu option as shown here. Select any date and add 1 minute between photos.
    3 - select just one photo from the album and create a book from it.
    4 - in the book click on the Options button ➙ Book Settings button and make sure the checkbox for Auto-layout pages is unchecked.
    5 - drag the album with your book photos onto the book icon and they will be imported into the Photos tray of the book in your pre-determined order but not into the pages themselves.
    OT

  • MIRO(Invoice Verification) posting date is lesser than MIGO(Goods Receipt)

    MIRO(Invoice Verification) posting date is lesser than MIGO(Goods Receipt) posting date.
    Explanation:
    Miro sholud be posted after the GRN has posted. It means that the Posting date of Miro should be greater than or equal to the Posting date of Migo. But I am facing the issue that I can able to post the Miro before the Migo date..
    For example:  I have posted the Migo(Goods receipt) document with the posting date u2013 10.8.09 and at the same time I can also able to post the Miro(Invoice Verification) posting date as u2013 5.08.09. This is should not be allowed . Kindly give me the solution. Is there any options in SAP standards to restrict this type of Postings(without using user exit).
    regards
    Varadharaj

    Hi
    you  need to use BADi for this INVOICE_UPDATE
    you can give logic as whil;e MIRO system will compare posting date with MIGO doc , then create a Z error msg in se91 nad assign it in that badi
    take help of ABAPer, check following link
    [LINK |GR date lesser than the PO date, the system should show an error message.;

  • Validation for posting date is less than 7 days of current date

    Hi
    I want to create a validation wherein  system will validate every entry that whether posting date is less than 7 days of current date. If it is than check in a set is that user id available if not than show error message.
    If someone have any idea on this logic pls share with me.
    Regd
    Shiv

    Hi,
    That's certainly possible via usual OB28 validation. Define your prerequisites for the posting date (you will have to do it via user-exit (bkpf-budat greater then sy-datum less 7 days) , and check whether the user is in the set.
    Regards,
    Eli

Maybe you are looking for