Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
CRM 2013 - Disabled Ribbon Buttons RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Can't find info on this anywhere so thought I would bring it up.

    I have a solution which was built for 2011 and had a number of Ribbon Buttons on forms which were disabled based on the Status of the form, usually via JavaScript.

    I am now testing the solution in 2013 and can see that none of these buttons are disabled anymore.

    Presumably this is due to the change in UI which seems to favour buttons simply being hidden rather than disabled.

    Is that correct?  Is disabling buttons now deprecated?

    Monday, October 21, 2013 11:35 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi.

    If the JavaScript you used is to access DOM objects of the ribbon buttons, they will not work in CRM 2013 (check details in SDK about DOM manipulation in CRM 2013)

    If you use supported rules to define them according to the value of a field to disable / enable ribbon buttons or command bars, they should work after the upgrade.

    Try to use RibbonWorkbench by Scott Durow, it will make your life much easier to customize ribbons or command bars

    Jaimie


    Monday, October 21, 2013 11:59 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi.

    If the JavaScript you used is to access DOM objects of the ribbon buttons, they will not work in CRM 2013 (check details in SDK about DOM manipulation in CRM 2013)

    If you use supported rules to define them according to the value of a field to disable / enable ribbon buttons or command bars, they should work after the upgrade.

    Try to use RibbonWorkbench by Scott Durow, it will make your life much easier to customize ribbons or command bars

    Jaimie


    Monday, October 21, 2013 11:59 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I amusing rules which are wired to JavaScript functions.  I'm guessing the issue lies there.

    Have heard good things about RibbonWorkbench.  Have used it briefly on another project a while ago.  Seeing as I will be validating the current solution against 2013 it will be time to have another look at.

    Monday, October 21, 2013 12:54 PM