{Dynamics CRM Plugins} Images and Filtering attributes not supported for Plugins for custom Actions in CRM 2013

In CRM 2013, Microsoft has introduced the concept of actions which is a wonderful way to represent you custom business functionality in the form of a request that CRM platform would understand. Also on top of that, you can register plugins for the actions you create. However there are certain limitations when using plugins with actions.

To illustrate this, lets start with a simple example.

Say we create an action for contact entity named new_TestAction” as shown in the screenshot below.

screen 21

Now we open the plugin registration tool and try to register a plugin on post execution of the action. As you can see from the below screenshot, filtering attributes are not supported in that case.

screen 22

Also let us try to register a post image on the plugin. As you can see from the below screenshot, CRM would not allow you to register that image and gives u an error.

screen 23

 

So if you have a requirement to register a plugin on post execution of an action, please keep these limitations in minds and design accordingly.

Hope this helps!

Advertisements

{Dynamics CRM Business Process} Change the Active Stage Flag in CRM 2013 Business Process Flows

Recently in our project, we had a customer requirement where the customer asked to change the colour of  image of active stage of a business process flow for Opportunity.

Let’s see how this can be achieved.

OOB in CRM 2013, the active stage flag for a business process in bluish is colour. Please check for the screenshot below.

screen 19

However, the customer wanted the flag to be in green to comply with their existing colour scheme. A little bit of exploring and we found that CRM picks up the image from the following location

<Installation Folder>\Microsoft Dynamics CRM\CRMWeb\_imgs\ProcessControl\process_control_global_active_flag.png

We took the .png image and modified the image using Photoshop to change the background colour to green keeping the dimensions exactly the same and then  replaced the old image with the new one. Recycle the app pool, clear your browser cache and refresh the page and the changes are reflected in the CRM. Check for the screenshot below.

screen 20

 

I would suggest you take a back-up of the original image before replacing the same. Also you have to do this as a part of your deployment once you move from dev–>test–>prod.

 

Hope this helps!

{Dynamics CRM Business Rules} Custom Xrm Script and Business Rules on the same Field in Dynamics CRM 2013

With the advent of Microsoft CRM 2013 in came business rules, a wonderful feature of the new CRM version. However with new implementations, there would be always some new confusions creeping up. Well in many training sessions on CRM 2013, i keep getting the question – “Will my onchange handlers and business rules work at the same time on the same field?”.

The best way to get the answer is to try out only. So let’s do a small test which i myself faced in one of my implementations. I was faced with a scenario where I had to to do whole lot of stuffs on change of field including clearing out certain other field values. All of them but clearing stuff was possible with business rules. So had to write a custom onchange event handler for the field. And yes both the business rules and my custom code triggered. Let’s see this with a simple example.

In the contact entity, for the email field I have a simple business rule which make the email field mandatory as soon as First Name field is entered/ changed by the user. Also for experimental purpose, I will register on on-change of First Name, to show a alert. Check for the screenshots below.

Screen 14

Screen 16

 

 

Now when I changed the First Name for a new Contact, first of all my custom jScript code fired. When I closed the alert by clicking OK, the Email field was set to Business Required by the Business Rule.

Screen 17

Screen 18

However remember the following MSDN Documentation – “When you set a field value by using a business rule, any OnChange event handlers for that
field will not run. This is to reduce the potential for a circular reference, which could lead to an infinite loop. ”

So when you are designing business rules and customer onchange handlers for your implementations, please do take all this into consideration.

Hope this helps!

{Dynamics CRM Social Pane} Hide Posts From Social Pane in CRM 2013

In CRM 2013 Microsoft introduced the Social Pane, also known as Record Wall. Recently in our project we had a requirement to disable posts for a particular security role. To do that the first thing we did is to remove the Post Privileges for the security role. Please refer to the screenshot below.

screen 12

As you can see, remove all the privileges for the POST entity from the security role.

However after this change is made, when the user logs into the application, this is how it looks to the user.

screen 13

However what we needed to do is to hide the Posts tab altogether for this security role. A little bit of searching and found the below link. This gave us exactly what we needed.

https://community.dynamics.com/crm/b/crmsoftwareblog/archive/2013/10/26/hide-post-tab-in-social-pane-microsoft-crm-2013.aspx

All you need to do is call the method HidePosts() as mentioned in the link in the onload of the form and check for the currently logged in users security roles. And then hide the  post tab if the security role matches the condition.

Hope this helps!

{Dynamics CRM Business Process Flow} Prevent user from moving to previous stage in CRM 2013 Business Process Flows.

In CRM 2013 Business Process flow, the user can move both forward and backward to next stage and previous stage respectively using the Next/ Previous arrows. However sometimes your requirement might be to have process flows unidirectional. In that case you would not want to show the previous arrow shown to the user. Let’s see how you can achieve this using  jQuery.

Following is a business process flow that we have set up for the opportunity entity.

Screen 10

As you can see, we have both the Previous and the Next Stage buttons here.

Let’s how we can hide the previous stage button

In google chrome, using developer tools, we can explore the HTML for the Previous Stage arrow. Following is the HTML that we have.

screen 11

The Id of the Previous stage arrow is stageBackActionContainer. All we need to do is hide this div and increase the width of the “Next stage” div so that it occupies the vacant space using the code below.

function hidePreviousStageButton(stageBackActionContainer, stageAdvanceActionContainer) {
$(“#stageBackActionContainer”).hide();
$(“#stageBackActionContainer”).html(“”);
$(“#stageAdvanceActionContainer”).css(“width”, “90px”);
}

All you need to do is call the hidePreviousStageButton in the onload of the form.

Hope this helps!

{Dynamics CRM} Control CRM 2013 Business Process Next Stage and Previous Stage flow using JScript.

Recently in our project we needed to restrict the business process flow from one stage to another depending on certain conditions. The problem was that OOB CRM 2013 does allow you to plugin your custom client side code when the “Next Stage” or the “Previous Stage” icons are clicked. You can obviously register Plugins and Workflows on the business process stage change but you cannot stop the change of stages using the same. Let’s see how we can achieve this.

Below is the screenshot of an example business process flow for opportunity entity. Let’s explore what CRM does here. I have opened Chrome Developer tools and trying to explore the HTML for business process flow. I have selected the ‘Next Stage’ button.

screen 9

The id of the div is “stageAdvanceActionContainer”.

So what we need to do is override the click event with our custom function and then if our condition meets we would call the OOB event handler. The code below does the same.

function  registerBusinessProcessEvents()

{

var originalNextStageHandler = $(“#stageAdvanceActionContainer”).data(“events”)[“click”][0].handler;

 

// unbind the original next event handler

$(“#stageAdvanceActionContainer”).unbind(“click”);

 

$(“#stageAdvanceActionContainer”).click(function (e) {

// perform your custom logic here. If you want to move to the next stage just call the code below.

 

$.proxy(originalNextStageHandler, $(“#stageAdvanceActionContainer”))(e);

 

}

 

}

All you need to do is call the registerBusinessProcessEvents  function during the onload of the form.

Similarly the ID for the previous click handler is “stageBackActionContainer”. And you can handle it in the same manner as above.

 

Please note that is an unsupported customization and might not work if Microsoft decides to change the id of the div elements or the rendering model in future rollups.

 

Hope this helps!

CRM 2013 Solution Import Error – An item with the same key has already been added

In CRM 2013, while importing of solution, we faced the error “An item with the same key has already been added”.

A little bit of searching and we found this very good article which describes how to resolve the error – http://nishantrana.wordpress.com/2014/04/15/an-item-with-the-same-key-has-already-been-added-error-while-importing-solution-in-crm-2013/

However as the link suggests, it was not possible for us to delete the field since we had some data where the field was populated in the target environment. Hence we had to take the alternate route.

We unzipped the customizations and looked for the field in the customizations.xml file.

For e.g. in the screen shot below, we could see the field with physical name “new_IsOpportunityCustomer”. However when we went into the customizations of the target environment the name was “new_isopportunitycustomer”. Clearly there was a difference in casing which led to the below error.

screen 8

To resolve this we changed the physical name in the customizations.xml from “new_IsOpportunityCustomer” to “new_isopportunitycustomer” and re-imported the solution and everything worked fine.

Hope this helps!