DYNAMICS 365 MOVE RIBBON BUTTON FROM ONE TAB TO ANOTHER

In this blog post, I will explain how to move a ribbon button from one tab to another.

Our victim will be the Run Report button on the Account entity views. However, this can be applied to any other button whether it is displayed on a View, Form, or Sub-grid.

The main purpose of this modification, is to increase the User Experience by saving one additional click to execute any action especially if it is frequently used.

Problem

Whenever you want to click Run Report button (in a view, form, or sub-grid), you have to select the record(s), click the (...) button, click Run Report button, and finally click on the report to be generated.
Move ribbon button 1

Solution

The below steps will guide you to change the location of the button in order to be directly clickable when the user selects a record(s) in a view.
  1. Install the Ribbon Workbench and add the Account entity to a new temporary solution
  2. Open the Ribbon Workbench and load the solution
  3. Select the Account entity from the list
  4. Click the Ribbon tab, and in Home Ribbon, scroll to the right to reach the Run Report button. (the same can be applied to the Form or Sub-grid)
    Move ribbon button 2

  5. Right-Click Run Report > Customize Button. You are now able to relocate the button
  6. Drag the button onto a tab where it can be directly shown in the view (before Send Direct Email button in this example)
  7. You will receive a message informing you that the old button will be hidden and a copy will be created
    Move ribbon button 3

  8. Click OK to accept the changes and create the copy of the button in the ribbon
    Move ribbon button 4

  9. Click Publish > OK to publish the changes to the organization
  10. After the publish is done, you can check that the Run Report button is now displayed in the command bar, and the user can directly click it
    Move ribbon button 5


Hope This Helps!

Comments

Post a Comment

Popular posts from this blog

DYNAMICS 365 HOW TO HIDE RECENT RECORDS FOR LOOKUP FIELD IN UCI

Image
In UCI, a lot of behaviors have been changed comparing to the Classic Web Interface such as the tabs, BPF, and many others. Today, I will be talking about one of these behaviors which is the Recent Records in lookup fields. In a brief summary, the Recent Records feature will suggest the latest records that have been searched for, where the user can select one of them, and, the list of available records of the current view will then be displayed. This is a nice-to-have feature since it might help the users to speed up data entry. However, if the lookup has been filtered to display specific records, the Recent Records will not respect this filter and will keep showing records even is they should not. This scenario can lead to selecting a record by the user that is not allowed to be selected. Therefore, in this situation, it is better to hide the Recent Records t
Read more

SEARCH BY GUID IN DYNAMICS 365

Image
Is it possible to search for a CRM record using its GUID ? Well, NO it is not possible and YES it is possible!!! As always has been, it is not possible to search for a record by its guid in Advanced Find and in the Quick view search. However, in the model-driven app Edit filters functionality, it is possible to search for a record by its Guid. How it works, let's check the 3 different places where we can search for a records. Advanced Find search Using the Advanced find feature, you cannot put a GUID value to search for. You will directly receive an error notification eventhough when you download the fetchXml, the Guid of the record will be there. Quick view search Using the search box
Read more

SAVE FORM IN DYNAMICS 365 JAVASCRIPT

Image
In Dynamics 365, you may need to save a CRM form automatically in JavaScript upon a specific action on the form. In order to do that, the function formContext.data.save(saveOptions).then(successCallback, errorCallback); can be used to save the record asynchronously with callback functions to be executed after the save operation is completed. The following example will display a successful message if the save operation is completed, and a failure message if not. formContext.data.save(1).then( function () { alert("Successfully Saved!"); }, function () { alert("Failed while saving!"); });
Read more