We will look at how we can use JavaScript to cancel flows that are running without canceling each flow manually. To do this, follow the steps below. Let’s look at a scenario where we are seeing the flows that are in a running state and are not terminating. Click on All runs, this navigates you to all flow runs view. When we are in the All runs view, we need to open the developer console in the browser. The developer console can be opened by clicking F12 (or holding fn and F12) on Windows. Or by right-clicking on the screen and clicking Inspect. In the developer console, navigate to the Console pane. To clear the console window, click CTRL + L. The console pane is where we will add the JavaScript code that will cancel the running flows. As can be seen in the next step. // Copy this first and run it in the console var jq = document.createElement(‘script’); jq.src=”https://cdnjs.cloudflare.com/ajax/libs/jquery/3.3.1/jquery.min.js”; document.getElementsByTagName(‘head’)[0].appendChild(jq); // … give time for script to load, then type (or see below for non wait option) jQuery.noConflict() //Paste the same again var jq = document.createElement(‘script’); jq.src=”https://cdnjs.cloudflare.com/ajax/libs/jquery/3.3.1/jquery.min.js”; document.getElementsByTagName(‘head’)[0].appendChild(jq); // … give time for script to load, then type (or see below for non wait option) jQuery.noConflict() // Then copy this in the console to start the cancelation of the flows. confirm = function () {return true;}; setInterval(function () { $(“.fl-StatusInCell:contains(‘Running’)”).parent().parent().find(‘.ms-DetailsRow-cell’).last().click(); $(‘button[name=”Cancel”]’).click(); },5000); Click the running code after the code is implemented in the console, and the output will be seen below Hope this Helps!

Use Case – To Switch form based on the value selected from option set field. Steps – 1. We have a Option Set field – “Lead Type“ Based on the Option selected – the form will switch For example – “PMO Member” – On change of the option, it will switch to PMO Member Form “HR” – On change of the option, it will switch to HR Form 2. To get the current form Guid use the following in the console- 3. Below JavaScript Code- Hope this helps!!

In today’s blog, we will cover how to change the BPF using JavaScript in the unified interface when the form loads based on a custom field Lead Type on the Lead form. Let’s take a closer look! Steps – In the example below, we have a new option set field called Lead Type with values of TAB Member and TBO. When the Lead Type has a value of TAB Member, update the business process flow to the TAB Member BPF and when the value is TBO, update the business process flow to TBO BPF. 2. Create two separate BPFs for the required entity. In this case, we created two separate BPFs for the Lead entity. 3.  From each BPF, grab the record GUID using the console. 4. JavaScript Code- Results – Hope this helps!!

Hi Everyone, If you are using Custom Pages in your Model Driven App and would like to have multiple languages as per User’s Personal settings? Here’s a quick helpful method for Custom Pages Step 1: Let’s start by creating a Custom Page Go to PowerApps Maker Studio, in your selected environment outside or inside a solution. Add new Custom Page Step 2: Fill your app as per requirement. I’ll just keep it basic. Note: OOTB Tables/Entities will show translated values except custom text/tooltip/custom tables, etc. Below, for my custom Title Label. I have used Language() function to detect the User’s language set in Personal Settings applied on Browser Level. Step 3: Save, Add and Publish the Page on Site Map (Edit in Preview) section. Reload your Model Driven App to see the effect User’s Language set as English User’s Language set as Spanish Select Spanish in Personal Settings That’s how simple it is to set Language in your Custom Page. Note: If you are working with Custom Entities, BPFs you need to add translation for the Language in Data verse manually. Please follow the steps mentioned in this Blog: Enable language translation on Custom solutions in Dynamics CRM. Hope this helps 🙂

In this blog we will see the steps in order to send a automated message via Teams as soon as an Opportunity is created in Microsoft Dynamics 365. Step 1: Go to portal.azure.com and select the Azure Logic App Resource. Step 2: Enter all the details such as the Name, Resource Group, Subscription, Region, etc. required while creating a Logic App. Step 3: Select the Dynamics 365 trigger When a record is updated. Step 4: Select Opportunities entity after setting by the Dynamics 365 CRM connection Step 5: Set the data refresh time as required. Step 6: Select the IF action in the next step and the condition would be status_label=won for true. Step 7: Inside True Block select Post a message in a chat or channel option. You can also handle the condition for False block, but in this case we can leave it blank. Step 8: You can post this message in a Group, Channel or send it as a Personal chat. Step 10: Wait for the trigger successful notification. Step 11: Go to Dynamics 365 CRM and navigate to opportunities entity. Step 12: Open a test opportunity or create one if doesn’t exist and close the opportunity as won. Step 13: As soon as you closed this opportunity you may have received the following message. Hence in this blog we saw how we can send messages on MS Teams using Azure Logic Apps on triggering certain conditions. Hope this helped!

In this blog, we’ll see how to apply language translation on custom entities, model driven apps and business process flows in Dynamics CRM Step 1- Go to Settings -> Administration->Languages. In Language settings select the required language and click on apply. Step 2- Include all the required components into the solution For example- Custom Entities Model Driven App- For example – Sales Hub Business Process Flow (BPF)- Include the BPF entity as well as process Step 3- Select the solution and click on Export Translation to export the translations to an archived file. Step 4- Extract the contents of the downloaded CrmTranslations_<solutionname>_1_0.zip. This will extract two files. Step 5- After extracting the file, open the CrmTranslations.xml file in excel. You will find 3 sheets in it. Open Localized Labels file, you will find columns for each of the languages you have deployed. Fill in the translations for each language options available. Step 6- Zip the file again and re-import the translations to the same solution using the Import translations button. Step 7- After successful import, click on publish all customizations. Step 8- Go to settings ->Personalization Settings -> Languages. Select the language you wanted to translate into. Output- Hope this helps!!

In this blog we’ll see how to integrate SharePoint with Dynamics 365. Step 1- Configure SharePoint Option in Dynamics 365 Document Management option. Go to Advanced settings -> Document Management. Step 2- In Document Management select “Enable Server-based SharePoint Integration” Step 3- Now in the pop-up screen provide SharePoint site location as “Online” then proceed to next. Step 4- Now provide a valid SharePoint URL and click on finish. Step 5- Enable Share point Document setting for Entities using Document Management Settings. Step 6- Now in the Pop-up screen select the entities that you want to use to manage SharePoint documents. You will find some entities like Account are already Enabled and if you want you can enable other entities. We can also add custom entities if required. Step 7- Check Based on entity, document libraries and folders that are based on Account entity are automatically created on SharePoint site. Step 8- We can store a document for an Account or for any other entity in SharePoint. Open an Account and click on Related tab to choose Document option. Hope this helps!!

Introduction: In this blog we will see how we can pass parameters to a JavaScript function where the function is generic and can be reused. Implementation: Let’s take an example where you would check if account number is present or not in the account field. 1. Create a JS function to check if account number is present in the Account field. 2. Add function to the Web Resource library in solution. 3. Adding it to the form of the Account entity to reflect the output on load of the page. 4. Checking for the result on load of Account. Hope this helps …

Introduction Below is the Syntax that’s available to create, delete, update a record in Dynamics 365 Online V9.X using JavaScript. Create record (Client API Reference) Below is the Syntax that’s available to create a record in Dynamics 365 Online V9.X using JavaScript Syntax : Xrm.WebApi.createRecord(entityLogicalName, data).then(successCallback, errorCallback); Implementation : Let’s take an example where you would like to Create the Account record. // define the data to create new accountvar data = { “name”: “Sample Account”, “creditonhold”: false, “address1_latitude”: 47.639583, “description”: “This is the description of the sample account”, “revenue”: 5000000, “accountcategorycode”: 1 }// create account recordXrm.WebApi.createRecord(“account”, data).then( function success(result) { console.log(“Account created with ID: ” + result.id); // perform operations on record creation }, function (error) { console.log(error.message); // handle error conditions }); Update record (Client API Reference) Below is the Syntax that’s available to update a record in Dynamics 365 Online V9.X using JavaScript Syntax :  Xrm.WebApi.updateRecord(entityLogicalName, id, data).then(successCallback, errorCallback); Implementation : Let’s take an example where you would like to Update the Account record. // define the data to update accountvar data = { “name”: “Updated Sample Account “, “creditonhold”: true, “address1_latitude”: 47.639583, “description”: “This is the updated description of the sample account”, “revenue”: 6000000, “accountcategorycode”: 2}// update the recordXrm.WebApi.updateRecord(“account”, “5531d753-95af-e711-a94e-000d3a11e605”, data).then( function success(result) { console.log(“Account updated”); // perform operations on record update }, function(error) { console.log(error.message); // handle error conditions }); Delete record (Client API Reference) Below is the Syntax that’s available to delete a record in Dynamics 365 Online V9.X using JavaScript Syntax : Xrm.WebApi.deleteRecord(entityLogicalName, id).then(successCallback, errorCallback); Implementation : Let’s take an example where you would like to Delete the Account record. Xrm.WebApi.deleteRecord(“account”, “5531d753-95af-e711-a94e-000d3a11e605”).then( function success(result) { console.log(“Account deleted”); // perform operations on record deletion }, function (error) { console.log(error.message); // handle error conditions }); Hope this Helps ….

In this blog, we’ll see how to create a button on ribbon by using ribbon workbench in XRM toolbox and on click, open quick create form. Step 1- Insert a ribbon button on any required record form using ribbon workbench on XRM toolbox. Step 2- Name the ribbon button (anything as required) Step 3- Add button properties- Give ID name Label name Icon for the button Step 4- Add the following code to open a quick create form on click of the button var RecordaMeeting = {     //RecordaMeeting.OpenRecord     OpenRecord: function (primaryControl) {         var entityFormOptions = {};         entityFormOptions[“entityName”] = “Add the entity name”;         entityFormOptions[“useQuickCreateForm”] = true;         var formParameters = {};         // Open the form.         Xrm.Navigation.openForm(entityFormOptions, formParameters).then(             function (success) {                 console.log(success);             },             function (error) {                 console.log(error);             });     }, Step 5- After adding the script, add the command for the button- Web resources library name Web resources function name CRM Parameter: PrimaryControl Step 6- Add command on button properties. Step 7- Publish the button. Screenshots of implementation: Step 8- Button appears on the ribbon for the required entity. Step 9- On click of button, quick create form opens. Hope this helps!!