Posts Tagged CRM 2013
One of the most powerful features introduced in CRM 2013 is Actions. It strongly supports the concept of XRM platform. Actions are the Custom messages which can be created for any entity or globally to perform business operations like create/update/Assign etc. (more than what a Workflow can do). Looking first time we get a feeling that it is very similar to Workflow but hold on it’s very different from WF’s or Plugins.Below are the key points which make it different:
- Can be associated with single entity or globally.
- Actions support Arguments – Input and Output Arguments.
- Supports Rollback and executes in real time.
- Always runs under the context of the calling user.
Arguments are the parameters or the variables which can be used while creating the action. There are two kinds of arguments
These are the parameters which need to be passed during action call. These can be Optional/Mandatory. For Mandatory argument it is necessary to provide some value while calling this action. These input arguments can be used as variables while performing any operation in the action.
These are the parameters which can be returned when the action is called. These can be Optional/Mandatory.
To understand in an easy way we can compare actions with a Function/method in normal C# programming which can have parameters and also can return something at the end.
Let’s take a look of the different types of Arguments it supports.
Let me create a simple Action on Enquiry entity which has one Input Argument: ProjectName [string]
To create this we need to navigate to Processes and select Category as Actions. In primary entity I am selecting Enquiry which is custom entity in my case. I have taken one Input Parameter- ProjectName. And in the step I am using this Variable during creating a Project’s record which is again a custom entity.
And here is the snap of the Step which I have configured. Here we can see that I am using this ProjectName as a dynamic value during the Project Creation. Here note that new_EnquiryCreateProject is the name of the Action which should be referred while calling this through API.
Calling Actions from Plugins
Now we can call this Action from our Plugin. I have a Plugin which fires on Post Create of Enquiry. There I am calling this Action. I am passing the Input Argument ProjectName as Parameter before calling this Action. Once this is called It creates a new Project record.
// Calling the Action - new_EnquiryCreateProject OrganizationRequest req = new OrganizationRequest("new_EnquiryCreateProject"); req["ProjectName"] = "This is a test operation for using Actions in CRM 2013 "; req["Target"] = new EntityReference("new_enquiry", enquiryObj.Id); //execute the request OrganizationResponse response = service.Execute(req);
And now the most Amazing part of Actions are that we can consider this as a unique message and can register this through Plugin registration tool and can do Custom Validations if we want to do during the execution time.
Let’s say during the execution of this Action I want to validate something or abort this Operation in certain conditions then we can easily do by registering this as a message which is a great example of Xrm support in CRM 2013 as now it is not restricted to messages like Create, update, delete etc.
Below it is shown how we can register this through Plugin Registration Tool.
Note: These actions are little bit different from Plugins as return type of the Target is not Entity but it is Entity Reference. During the execution of this Action we can get the Input Arguments and use this for any type of validations.
Below is the sample where I am reading the values of the Target and the Input Argument ProjectName used in the above example.
Here we can clearly see that the context contains only 2 values one is the Parameter and the other one is the Target.
As a developer, introduction to Actions in this CRM 2013 release is really a great improvement from CRM’s perspective which will help us to minimize the coding part and also achieve some complex requirement easily.
Wow!!!! It sounds great… Let us have a quick walk through of this new feature and see how we can incorporate this for our requirements.
When a lead source is changed to Partner – I want to make
1. Business Phone and Email as Mandatory Fields
2. Hide the Mobile Phone Field
Now let us create a Business Rule to meet the above requirement. Business Rules comes as a part of your entity in the solution as shown below.
Go to Business Rules for Lead entity and Create a new one. Here we can notice that we can do the following things
1. Add Conditions
2. Add Actions
3. Provide Description
In this example we have added one condition as if the lead source is Partner. In actions we can see that we are making the Business Phone as Mandatory, Hiding the Mobile Phone field and Making the email as Mandatory.
There are very limited options available for the creating the actions like as shown below.
Once we are done with the creation part we need to save this and activate. Similar to Processes we can activate and deactivate this Rules at any point of time. Also if we have multiple forms then we can also define for which forms these rules should be applied.
One good I liked the most is that there is a Save As Option available so we can create multiple rules in minute and then edit accordingly.
Key points to be noted
2. It does not supports hiding/Showing Tabs and Sections.
4. Well supported in Mobiles and Ipad.
5. Rules can be applied form wise. So in case of multiple forms you may specify for which forms these rules is applicable for.