Using FormContext as Global variable in D365

Hello Guys,

This blog will explain the use of Form Context or Execution Context as Global variable in D365.

We know that Client Side Scripting using Java Script is one of the best way to handle business process logic whether it is a client side validation or displaying data on model driven app.

For implementing this functionalities one of the main feature is Xrm.Page which is deprecated now and we have to use Execution Context instead of this. To use Execution Context we need to pass it as parameter in Java script function as shown in below image.


Consider a scenario where we are having multiple functions which is using Execution Context on single entity. Now to implement this either we can pass execution context as first parameter in all function as shown above image or we call function by passing parameter in it. This approach is fine when we have less functions but what about where we are working on large functions used in a single entity.

In this scenario we can use Form Context or Execution Context as global variable.
Also there are some scenario where we need to use Primary Control while working with ribbon workbench. Here we need to pass Primary Control CRM Parameter.

We can handle both the scenario as single approach and that is use Form Context as global variable. You can implement below steps to achieve this.

Step 1: Create one Java Script file in Visual Studio or in any editor which you prefer. And Paste below code:


Step 2: Upload this Java Script as web resource in D365.


Step 3: Select Entity on which you want to add this function. For example, In below image we have used contact entity. Open Form Editor and Click on Form Properties. Click on ADD button in Form Libraries Section to add Web Resource. Once Web resource is added then select Form Control and select it's OnLoad event and click on ADD button.


Step 4: Select library and specify the function name and check the check box that is Pass execution context as first parameter and click on OK. Publish the customization.



Step 5: Now you can use FormContext variable in other functions too. You don't need to pass it as first parameter again. Also you can use the same variable while working with Ribbon workbench as you don't need to pass primary Control as CRM Parameter.

Hope it helps...














Comments

Post a Comment

Popular posts from this blog

Read Only Sub Grid & Editable Sub grid in Dynamics 365

Image
Hello Guys, In my previous blogs we have seen Duplicate Detection in Dynamics 365 where we covered how you can use OOB feature of D365 to detect duplicate records. Today we will see how we can implement editable sub grid.  But before if you are new to our blog then do follow us to know more about Dynamics and Power Platform. Also if you like our blog then please comment and share this blog with your friends. In Dynamics CRM we have seen many entities sharing parent child relationships and we can create records of child from the parent page. For example Account and Contact Entity. We can create a new contact entity from the Account Form with the help of Sub Grid control. We can also create sub grid for custom entity and can utilize it in our own way. We will be using Department and Employee Entity for demonstration. Below are the steps: Step 1:- Login to Dynamics 365 with credentials. Step 2:- Click on Advance Settings Gear icon. Navigate to Settings -> Solution -...
Read more

Using Pipelines in Power platform for deploying solutions to environments.

Image
Hello Guys, In our previous  blog   we have seen how to use changesets in PA flow for atomic transactions. Today we will see how we can use Power Platform pipeline for deploying solutions. Do follow us to know more about Dynamics and Power Platform.  Also if you like our blog then please comment and share this blog with your friends. AS a CRM Developer, we need to create and manage solutions for various environment. Once development is done on Dev environment, we are moving the CRM changes by packaging into the solution to next environment like UAT and Production. Previously we were doing the solution movement manually but nowadays we have CICD pipeline in Azure. Now Microsoft has introduced pipelines in Power Platform too. So today we will be exploring the same Pipeline and will see how to deploy solutions in various environment using Power Platform Pipeline.  As you can see in above image, we have three environments like Dev, UAT and Prod. We will be doing some cus...
Read more

Understanding Sales Process in D365.

Image
Hello Guys, In our previous blog we have seen what is Lead and types of leads. Today we are going to understand Sales Process. Do follow us to know more about Dynamics and Power Platform. Also if you like our blog then please comment and share this blog with your friends. Sales Life cycle begins with Lead. Business captures leads through advertising, marketing, trade shows, mailings etc. Whenever organization gets any new lead, Sales Person captures the information of the lead in Lead entity available in Dynamics 365. For creating lead we require only two things, Lead Name and a Topic describing the lead. Once lead creation is completed, Sales Person performs follow up activities by sending emails, appointment and phone calls to collect more information about the lead. Microsoft Dynamics 365 stores these activities in the Activities entity in the system. Leads can be qualified or disqualified. A disqualified lead indicates that the lead is not a good candidate for sales opportunit...
Read more