Creating a Log Analytics Workspace in Azure is an essential step for monitoring and analyzing data from various sources within your Azure environment. This guide will walk you through the process, providing clear instructions and tips to help you set up your workspace efficiently. Azure Log Analytics Workspace is a powerful tool that allows you to collect and analyze data from various sources within your Azure environment. It provides insights that help you monitor the performance, availability, and health of your resources. Setting up a Log Analytics Workspace is crucial for effective cloud management and optimization. Access the Azure Portal – Log In: Start by logging into the Azure Portal. – Look for Log Analytics: Type “Log Analytics Workspaces” into the top search bar and choose it from the drop-down menu. Create a New Workspace – Initiate Creation: Click on the “Create” button to start the process. – Resource Group: To arrange your resources, select an already-existing group or establish a new one. – Name: Enter a unique name for your Log Analytics Workspace. Review and Create – Review Details: Check all the details you have entered to ensure they are correct. – Create Workspace: Click “Review + create,” and after validation, click “Create” to deploy your workspace. – If you go to Logs, you will have the ability to query the logs: Benefits of using Azure Log Analytics Workspace Practical Applications We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Integrating Azure Logic Apps with the Common Data Service (CDS) opens up a world of possibilities for automating business processes and enhancing productivity within your organization. This blog will guide you through the steps to set up this integration, explaining the benefits and practical applications along the way. Azure Logic Apps is a powerful cloud-based service that allows you to automate workflows and integrate apps, data, and services across organizations. The Common Data Service, now known as Dataverse, provides a secure and scalable data storage solution that supports integration with various Microsoft and third-party applications. By integrating these two services, you can streamline data flow and automate complex workflows with ease. Prerequisites Before you begin, ensure you have the following: – An active Azure subscription. – Access to the Common Data Service (Dataverse) environment. – Necessary permissions to create and manage Logic Apps and CDS. Log in to the Azure Portal: Go to Azure Portal. Create a New Logic App: – Search for “Logic Apps” in the search bar. – Click on “Add” to create a new Logic App. – Fill in the required details (name, resource group) and click “Create”. Add a CDS Connector: – Once the Logic App is created, open the Workflow and Add one. – Click on “When a row is added” under Common Data Service triggers. – Sign in to your CDS environment and grant the necessary permissions. Configure the Trigger: – Select the relevant entity – Accounts and specify the trigger conditions – When a row is added. – Accordingly, when a record is added then create a Contact Record. – Save the Logic App Testing Out: Scenario – Create a new account in your Dynamics 365 / Power App. After a few moments, refresh and we see the contact has been created and assigned to the new Account. – So, we know our Logic App has run. Now let’s look at it in the Azure portal. Under Metrics, we see the Logic App has run. Why Integrate Azure Logic Apps with Common Data Service? We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction –   A few years ago, Dual Write (DW) was introduced with the objective of providing a reliable integration between Dynamics CRM and Dynamics Finance & SCM. The intent is in the right direction, but the execution of this vision has not been reliable.   In this blog we have talked about some of the challenges we have faced and our recommendations for reliable integration.   Let’s look at some of the challenges we have faced –  Initial Sync Limitations –  Unavailability of solution in few regions –  Enabling Solution issue and missing File –  Billing Rule Error –  Table Version mismatch –  Other Issues –  Recommendations for reliable integrations –  We hope you found this article useful and if you would like to discuss anything you can reach out to us at transform@cloudfronts.com 

One way to lock down a form is through JavaScript. Let’s go through how to do this by looking at the code. var formCustomizations = { disableForm: function (executionContext) { let formContext = executionContext.getFormContext(); let formControls = formContext.ui.controls; formControls.forEach(element => { if (element.getName() != “” && element.getName() != null) { element.setDisabled(true); } }); } } Here when the JavaScript Function Is called and the execution parameter is passed, the user can see the desired output. formContext.ui.controls; Provides the properties and methods to retrieve information about the user interface (UI) controls for several sub-components of the form. formControls.forEach(element => { if (element.getName() != “” && element.getName() != null) { element.setDisabled(true);} Here the forEach loop will traverse and see if there are any fields that are not blank and the field value is not null, then set all that fields to read only on that form. Hope this helps!

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!

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 Autonumbering feature is useful to uniquely identify records and comes in handy when there are many records to filter. This blog will be the walkthrough for steps need to be performed in order to enable the auto numbering for field service entities. Lets take a scenario, there is a need to auto number the Work Order entity. So, let’s begin with the steps to configure the same. Step 1: Navigate to ‘Field Service Setting’ area and click on ‘Auto-Numbering’ button on ribbon bar. Now we can enable the auto numbering for Work Order entity. Click on ‘# Auto Numbering’ button. Step 2: This will open the pop-up window to Configure Auto-Numbering and ask you to select the entity for which you want to enable the auto numbering. So, select Work Order from the drop-down list. Step 3: Enter other configuration details as shown in the below screenshot. Let’s consider that we have 2000 existing work orders in CRM. The numbering for next work orders should start from 2001 with Field Service Auto numbering. For this we need to specify the Starting Number as ‘2001’. Click on ‘Apply’ in order to apply the changes. Step7: After clicking on Apply a message will be displayed — ‘Work Order settings have been successfully updated’. Now, Work Orders are ready for auto numbering and whenever new Work Order is created, Work Order number will be auto numbered from ‘2001’ since we have provided Starting Number as ‘2001’ in the configuration. Conclusion ‘Auto Numbering’ feature allows us to auto number the field service entities in field service and avoid duplicate records in CRM.

Introduction: Let’s say we want to set an icon for a button on a form in Dynamics 365. We will use the Ribbon Workbench to do this. Let’s add this to our Quote form. First, create a solution and add Quote Entity: To add buttons, we will use SVG images. For the Web Client, we will use PNG images. There are online tools ( https://www.iconfinder.com/) to download these 2 formats. Let’s create a Approval button with approval images and save it as a Web Resource. PNG file: SVG file: Now open the Ribbon Workbench: Add a new button to the Form, and add the PNG and SVG images from above. The PNG images are Image 16 and Image 32, and the SVG image is Modern Image, then Publish: Once published, go to the Unified Interface app and pull up an Account. You will see the new button: 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 ….

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 …