Category: Blog

Here’s a shortcut guide to customising the Form ribbon in CRM 2011.  Rather than explaining all of the intricacies of the ribbon here’s a set of instructions that will get a button added to a form with the least amount of steps/complexity.  In this scenario we will add a button to the Account form that will launch an external web page (if you prefer the button executes a jscript function keep reading as I cover that as well)… 

Here’s the steps:

1. Create a new Solution called Ribbon.

2. Add to your Solution the Account entity and then export the Solution.

3. Determine the location ID for where you want your button to sit (note: this take a bit of research, keep reading…)

3a. Download and install the CRM SDK.  Then go to the following SDK folder:

[UPDATE: 14 Dec 2011 – The latest SDK did not include the ribbon definition XML files forcing you to build and run an app from source code provided in order to generate them for your self. I provide instructions on this process here]

3b. Open accountribbon.xml in Visual Studio.

Now we need to find the relevant bit of XML that defines the ribbon component we want to customise.  Each entity has ribbon definitions for it’s form ribbon (“Form”), for the ribbon that appears when the entity’s grid view is selected from the main CRM menu (“HomePageGrid”) and for the ribbon that appears when the entity is displayed as an in-line grid on either a dashboard on another entity’s form (“SubGrid”).  You will see Tab definitions for each of this:

We are interested in the Form ribbon so minimise the other XML elements and have a look at the Tab definitions for the Account Form.  You will see 3 tabs are defined:

These are the definitions behind the “Account”, “Add” and “Customize” tabs you see when looking at the Account form in CRM:

The Tab that we want is the one that appears as “Account”.  The Tab definition for this is:

To add a button to the CRM ribbon we need to specify a location.  The value we need is the “Controls Id”.   Find the button you want your button added next to and grab the “Controls ID” that button sits under.  We will add our button to the “Process” Group next to the “Run Workflow” button so the Controls ID value we want is:

3c. Copy the Controls Id value to NotePad

3d.  Close accountribbon.xml

That’s our research done, let’s get back to defining our button…

4. Open the customisation.xml file that was included in your exported Solution zip file (open in Visual Studio).

5. From the XML menu, click Schemas and then add from .. sdkschemas the 3 xsd files that have “ribbon” in their name and also customizationssolution.xsd (this gives us intellisense)

7. Back in the main window of VS do a Find on “RibbonDiff” and then swap out: “<CustomActions />”  with:

01


02


03


04


05


06


07


08


09


10


11


12


13


14


15


16


17



<CustomActions> 


  <CustomAction Id="GT.account.Form.Star.CustomAction"


                Location="Mscrm.Form.account.MainTab.Workflow.Controls._children"


                Sequence="1"> 


    <CommandUIDefinition> 


      <Button Id="GT.account.Form.Star.Button"


              Command="GT.account.Form.Star.Command"


              LabelText="Star"


              ToolTipTitle="Tip"


              ToolTipDescription="This is a Star"


              TemplateAlias="o1"


              Image16by16="$webresource:new_star16x16"


              Image32by32="$webresource:new_star32x32"


      /> 


    </CommandUIDefinition> 


  </CustomAction> 


</CustomActions>

If you want to deviate from my scenario of customising the Account form the relevant bit in the above is the Location reference.  This is where the Controls ID value that we we obtained from our research goes.  Note: The Controls ID value needs to be appended with “._children” e.g.:

8.  If you have 16×16 and 32×32 icons for your button go and add those into CRM as web resources and then change the references in the above code snippet.  Otherwise, remove theImage16by16 and Image32by32 lines (they’re optional, the button will still show).

9. Scroll down a bit and replace: “<CommandDefinitions />”  with:

1


2


3


4


5


6


7


8


9


10


11



<CommandDefinitions> 


  <CommandDefinition Id="GT.account.Form.Star.Command"> 


    <EnableRules> 


    </EnableRules> 


    <DisplayRules> 


    </DisplayRules> 


    <Actions> 


      <Url Address="http://www.google.com" /> 


    </Actions> 


  </CommandDefinition> 


</CommandDefinitions>

10.Adjust the Url reference to whatever you want.  You can use use a relative reference if you want to launch a CRM URL or an HTML page you have loaded into CRM.

If you want to execute a jscript function instead swap out the <Actions> node with a jscript web resource and function name reference like the below:

1


2


3


4


5



<Actions> 


  <JavaScriptFunction Library="$webresource:new_getcontact"


                      FunctionName="NewCaseOnClick"


                      /> 


</Actions>

11. Save your customisation.xml changes.

12. Re-zip your unzipped solution back into a solution zip file, import, publish all and then refresh your browser.

Done.  

This solution is available for download in both managed and unmanaged formats.

Here’s a shortcut guide to customising the Form ribbon in CRM 2011.  Rather than explaining all of the intricacies of the ribbon here’s a set of instructions that will get a button added to a form with the least amount of steps/complexity.  In this scenario we will add a button to the Account form that will launch an external web page (if you prefer the button executes a jscript function keep reading as I cover that as well)… 

Here’s the steps:

1. Create a new Solution called Ribbon.

2. Add to your Solution the Account entity and then export the Solution.

3. Determine the location ID for where you want your button to sit (note: this take a bit of research, keep reading…)

3a. Download and install the CRM SDK.  Then go to the following SDK folder:

[UPDATE: 14 Dec 2011 – The latest SDK did not include the ribbon definition XML files forcing you to build and run an app from source code provided in order to generate them for your self. I provide instructions on this process here]

3b. Open accountribbon.xml in Visual Studio.

Now we need to find the relevant bit of XML that defines the ribbon component we want to customise.  Each entity has ribbon definitions for it’s form ribbon (“Form”), for the ribbon that appears when the entity’s grid view is selected from the main CRM menu (“HomePageGrid”) and for the ribbon that appears when the entity is displayed as an in-line grid on either a dashboard on another entity’s form (“SubGrid”).  You will see Tab definitions for each of this:

We are interested in the Form ribbon so minimise the other XML elements and have a look at the Tab definitions for the Account Form.  You will see 3 tabs are defined:

These are the definitions behind the “Account”, “Add” and “Customize” tabs you see when looking at the Account form in CRM:

The Tab that we want is the one that appears as “Account”.  The Tab definition for this is:

To add a button to the CRM ribbon we need to specify a location.  The value we need is the “Controls Id”.   Find the button you want your button added next to and grab the “Controls ID” that button sits under.  We will add our button to the “Process” Group next to the “Run Workflow” button so the Controls ID value we want is:

3c. Copy the Controls Id value to NotePad

3d.  Close accountribbon.xml

That’s our research done, let’s get back to defining our button…

4. Open the customisation.xml file that was included in your exported Solution zip file (open in Visual Studio).

5. From the XML menu, click Schemas and then add from .. sdkschemas the 3 xsd files that have “ribbon” in their name and also customizationssolution.xsd (this gives us intellisense)

7. Back in the main window of VS do a Find on “RibbonDiff” and then swap out: “<CustomActions />”  with:

01


02


03


04


05


06


07


08


09


10


11


12


13


14


15


16


17



<CustomActions> 


  <CustomAction Id="GT.account.Form.Star.CustomAction"


                Location="Mscrm.Form.account.MainTab.Workflow.Controls._children"


                Sequence="1"> 


    <CommandUIDefinition> 


      <Button Id="GT.account.Form.Star.Button"


              Command="GT.account.Form.Star.Command"


              LabelText="Star"


              ToolTipTitle="Tip"


              ToolTipDescription="This is a Star"


              TemplateAlias="o1"


              Image16by16="$webresource:new_star16x16"


              Image32by32="$webresource:new_star32x32"


      /> 


    </CommandUIDefinition> 


  </CustomAction> 


</CustomActions>

If you want to deviate from my scenario of customising the Account form the relevant bit in the above is the Location reference.  This is where the Controls ID value that we we obtained from our research goes.  Note: The Controls ID value needs to be appended with “._children” e.g.:

8.  If you have 16×16 and 32×32 icons for your button go and add those into CRM as web resources and then change the references in the above code snippet.  Otherwise, remove theImage16by16 and Image32by32 lines (they’re optional, the button will still show).

9. Scroll down a bit and replace: “<CommandDefinitions />”  with:

1


2


3


4


5


6


7


8


9


10


11



<CommandDefinitions> 


  <CommandDefinition Id="GT.account.Form.Star.Command"> 


    <EnableRules> 


    </EnableRules> 


    <DisplayRules> 


    </DisplayRules> 


    <Actions> 


      <Url Address="http://www.google.com" /> 


    </Actions> 


  </CommandDefinition> 


</CommandDefinitions>

10.Adjust the Url reference to whatever you want.  You can use use a relative reference if you want to launch a CRM URL or an HTML page you have loaded into CRM.

If you want to execute a jscript function instead swap out the <Actions> node with a jscript web resource and function name reference like the below:

1


2


3


4


5



<Actions> 


  <JavaScriptFunction Library="$webresource:new_getcontact"


                      FunctionName="NewCaseOnClick"


                      /> 


</Actions>

11. Save your customisation.xml changes.

12. Re-zip your unzipped solution back into a solution zip file, import, publish all and then refresh your browser.

Done.  

This solution is available for download in both managed and unmanaged formats.

For the scope of this article, I assume that you are familiar with C# OOP concepts and C# projects.

Let’s see how 
For this article I will create a default Contact whenever anyone creates an account.

For example, If an employee of an organization creates an account then a default contact with basic details should be added to that account automatically (using a plug-In).

Procedure

Step 1

Since we need to trigger our plug-in when an event is executed, we need to get the service of IPluginExecutionContext using the IServiceProvider object.

1. IPluginExecutionContext context = (IPluginExecutionContext)serviceProvider.GetService(typeof(IPluginExecutionContext));  

And the GetService method returns an object of the specified type. We need to type caste that object. 

Step 2

Plugin execution is an object with a property called InputParameter. 

Now when you know, we have a value in the target and it’s an Entity. 

We can typecast it into an Entity and using its logicalname property we can determine if the current executing event is for an account Entity or not.

And if it’s an account entity we can write our creation of contact code here and associate that contact with the currently executing account.



Step 4: The last step is to create an Organizationservicefactory instance and we need to create a new plug-in, add a pluginexecutioncontext object ID to create an Organization service and based on that service client we can create our custom Event. 

1. IOrganizationServiceFactory servicefactory = (IOrganizationServiceFactory)serviceProvider.GetService(typeof(IOrganizationServiceFactory));  
2. IOrganizationService client = servicefactory.CreateOrganizationService(context.UserId);   
3. client.Create(createcontact);  

Step 2
After logging in successfully, click Register > Register New Assembly.



Browse to the DLL you just created and click OK. 

Step 3

This Window includes an option for how and when you want to execute or fire your assembly or plug-in. 

Message: It defines on which event you want to run the plug-in.

Example: Create.

Primary Entity: It define on which Entity execution you want to run the plug-in.

Example: account.

Event pipeline stage of Execution: It defines when you want to run the DLL, before the core operations or after the core operations.

Execution Mode: Execution can be synchronous by default or can be asynchronous (that will be handled further by the Dynamic CRM Queue manager).

Deployment: Server where every plug-in is deployed.

Offline where you can deploy it on Outlook for offline use. 

Click Register New Step and whoo, it’s done.

Your assembly or plug-in is deployed on the server. Now go to Dynamic CRM and create an account, an automated contact will be added by default in that account without any manual entry from employees.