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!!

Introduction: In Dynamics 365, you can hide and show fields using JavaScript. This is useful if you have business logic that determines if fields are displayed or not to the user. Implementation: Let’s take an example where you would like to hide the Account field if the Contact field is populated. Next, we can check if the Contact field is empty using getAttribute(“fieldname”).getValue(). If empty, we can hide the field using setVisible. Let’s add this to the change event of the Contact field: function showAccountOnChange(executionContext){ formContext = executionContext.getFormContext(); if (formContext.getAttribute(“parentcontactid”).getValue() == null) { formContext.getControl(“parentaccountid”).setVisible(false); } else { formContext.getControl(“parentaccountid”).setVisible(true); }} When Contact field is populated, the Account field is displayed: When empty, the Account field is hidden and the field collapses (note this is v9 Dynamics 365): Hope this helps …

Customer Engagement apps running on a web browser on an iOS or Android tablet provide a similar experience to using it with a web browser on your desktop or laptop computer. However, some features are not available on the mobile app or mobile web browser out of which one is running SSRS reports. Let’s say we need to run a Sales History report as below on a web application. But on mobile but there is not Reports Menu/Button on mobile application. We can use the following work around with Model Driven apps. Step :1 Run the Report 1st time on the web browser and copy the URL.Step Step : 2 Open App designer Step: 3 Create a URL Menu Submenu Item and paste the about URL in the URL field. Step: 4 Save and Publish the app and you can see the same menu appearing on the mobile app # Run the report and it will open on the mobile browse you may continue with the same login credentials. [/vc_column_text][/vc_column][/vc_row]   Hope this helps!

Introduction – In this blog, you will learn about how we can perform different operations such as disable, enable, hide, etc. on D365 CRM Business Process flow using JavaScript. Set value in Business Process Flow Disable field on Business Process Flow here cf_outreach is the schema name of the field on BPF. for BPF we need to write header_process before the schema name of the field Enable field on Business Process Flow Hide a field on Business Process Flow Mark Field Required on Business Process Flow Mark Field Optional on Business Process Flow Mark field recommended on Business Process Flow

In this blog we will see how to integrate teams with Dynamics 365 for custom entities using Postman. Solution Step 1- Go to portal.azure.com and select Azure Active Directory. Step 2- On App Registration, click on new registration Step 3-Register an application and follow the steps: Name, Select Multitenant, Enter the required url. Then, click on register. Step 4- Add API permissions and add a permission. The request API permission window will appear where you need to select Dynamics 365. Step 5-The permission window appears and select Dynamics 365 Step 6- As you select Dynamics CRM you will be presented the permission window. Select “Delegated permission” and check the User Impersonation then click Add Permission button. Step 7- After permissions assigned, Grant admin consent confirmation: Click on yes. Step 8- Go to Manifest and change “allowPublicClient”: true Step 9- Go to Overview, save client ID Variable Name URL url https://Dynamicsurl.dynamics.com/ Version 9.0 Webapiurl {{url}}/api/data/v{{version}}/ Client ID Client ID from overview callbackurl http://localhost authurl https://login.microsoftonline.com/common/oauth2/authorize?resource={{url}} Step 10- Go to Postman, create a new environment and enter all the details in the table Step 11- Now connect to the environment from top right most corner. Step 12- Then create a new request Step 13-Include the following in body: Put status as Enable: true Logical Entity Name: Schema name of the entity. Step 14- Go to Authorization  From the Dropdown Select OAuth 2.0.Now we will provide the variable values to generate token. Give a name of token Choose Grant Type Implicit and provide corresponding variables for Callback URL, Auth URL and Client ID. Then click Get new Access Token. Now click on Get New Access Token Step 15- Now click on Get New Access Token Step 16- It will prompt you to login Dynamics 365 after you provide your authentication the token will generate. Step 17- Now, click on use token. Step 18- Click on send button Step 19- Now, collaborate button will be visible in ribbon for required entity. Hope this helps!!

MS Forms offers a functionality to create a dropdown field which is similar to an option set fields in D365 CRM, But when it comes to mapping or storing values between these two field things become a bit tricky. However there are a few workaround using power automate capabilities. In this blog let’s see how we can store a MS Forms Dropdowns options into an Option Set field in CRM.  What is an Option Set? Option sets are a field type that can be created within Dynamics CRM and are Often referred to as “dropdown” or a “pick-list”.   An option set has two identities for each of its option. The Options Label Name and the Label Value as shown in the below snapshot.  What is a Dropdown in MS Form ? A dropdown is a list of defined options(Choice) that can be selected by a user, unlike a text field where the data can be “organic” or manually entered.  Now Let’s Consider an use case :  Consider we have a MS Form Name “Company Registrations” when a user submits this form a Power Automate flow is triggered which creates a new Account record in CRM with the field mapping shown in similar colors in the below snapshot.   Now we need to get the form responses first to create a new Account record.  2. All the Text field values can be directly mapped into the dataverse connector as shown in the below snapshot.  3. For mapping the MS forms Dropdown to the Option set we need to maintain the CRMs Option Label values into our flow as to set (define the value of the option set) Option Sets in CRM we need to pass the Label Values to the flow (if you just pass the label text it won’t work hence we need to maintain these option set values in the flow)as shown below.  4. Now we need to select the option set field in our flow connector and select enter custom value.  5. Once you are able to add a customer value use the following expression which will dynamically bring option set label value for the dropdown choice selected by the user on the form.Expression – outputs(‘Option_Set_Values’)?[outputs(‘Get_Form_Response’)?[‘body/rf98dd4fb83624fc7b7314de77542a3ef’]]Red : Text in the above expression corresponds to “Outputs “in the below snapshot which is the output of the compose in which we stored our option set label values. Blue : Text corresponds to the “Ownership Type” from the form response.   Output : MS Form Submission –   Created Account Output –   Hope this helps !  

To keep track of all your customer data in one place, you may want to import contacts, leads, or other record types into Dynamics 365 Customer Engagement (on-premises) from other sources, such as from an email program, a spreadsheet, or your phone. In this blog we will be looking on how to import bulk data from excel and populating it in Microsoft Dynamics 365 CRM. Use Case: Importing Bulk amount of Leads into Microsoft Dynamics CRM. Solution: Step 1 : How to download a template for data import Go to Settings > Data Management > Templates for Data Import. Select the entity that you want to import the data for from the drop down list, then click Download. (Note) You can use a text file, a compressed zip file, an Excel spreadsheet, or Excel workbook to do the data import. The template will have the fields of that particular entity as the columns to be filled by the user. Adding all the details for the lead to be imported. Step 2 : How to import leads with a template Go to Settings > Data Management > Imports. Click on Import Data > Browse. Choose the file you’d like to upload, then click Next. In this example, I used Lead.xls. (Note) If you used a template for the lead upload, your data will automatically be mapped. If not, see Above for how to get a template for the upload. 4.) Set the owner on the Review Settings and Import Data screen, then click Submit. Once submitted, your lead will show up on the My Imports leads screen. When the upload is completed, the status will show as “Submitted.” 5.) Open Dynamics CRM to see whether the data has been imported or not as in the excel sheet. You can further use this according to your requirement either to import Accounts, Contacts and for many other Entities related customizations. Hope this helps !

On some instances, there are Managed fields in Dynamics 365 CRM (or CE if you want to call it) where we can’t change the required level of the field from Fields i.e. on the database level. And you get the below error – Here’s an alternative way to do it. Scenario Let’s consider this scenario. Although Microsoft suggests you don’t change the behavior of Managed fields since they are designed with a purpose. However, let’s consider this scenario where you want to make the Parent Account for Lead as required on the form.When you try to change the Requirement Level as follows And while saving this change, you get this error. So how do we do it? Let’s see. Workaround – Business Rule Now, to overcome this particular scenario you can implement a simple Business Rule to make it required as follows – If the field can’t be made Required on a database level, you can make it required on the form using Business Rule. Here’s how you create your Business Rule.As the Business Rule starts with the condition, here’s the check you need to add in case the field value is not entered. The condition I used is as below – Check if Parent Account for lead Does Not Contain Data If this is True, then go ahead and add a Step for True condition. Add Set Business Requirement Level And in this, you need to set the Business Required Status to Business Required as show below. And the result is the Business Rule which looks like in #1 above. Now, save your changes, Publish the Rule, Activate and check. The result will be that the field is not required once it doesn’t have data forcing the user to enter data for the same. Hope this is helpful!

In this blog, we will see how we can show activities on Notes in D365 CRM.  Step 1 – Click on Entity and check marked Activities. Save and publish the Entity. Step 2 – Open Main form where you have added timeline, Double click on timeline notes and mark filter by as Show all. Save and Publish the form. Output before enabling the activities Output after enabling the activities