Introduction: Microsoft’s Voice of the Customer (VoC) application, part of Dynamics 365 for Customer Engagement, empowers users to create surveys without the need of a third-party product. Some elements of the experience can be configured in VoC like logos and custom images. The theming layer allow users to edit a survey’s look and feel with custom colors and other details using CSS to align with the organization’s brand. In this article, we’ll take a look at how to customize a response page and setup a redirection link to the thank you page. The problem: Customizing a thank you GIF image: One of our retail industry clients had a requirement of adding a “thank you” GIF image and another linked image to their survey thank you page. When clicked, the linked image would take the survey respondent back to the first page of survey. But VoC has no such default customization functionality on its thank you page. Solution: Since it is not possible to meet this requirement using VoC alone, we tricked the program with CSS. Here’s what we did: 1. Go to active surveys and click the survey that you want to modify. 2. Go to survey designer and select “Complete Page,” which is the page seen upon completion of the survey. The survey designer section shows your complete survey, with all elements. You can design your survey here with desired questions, their types, and can even add pages to your survey. The thank you page, or complete page, is the last page of the survey and the one in need of customization, per the customer’s requirements.  I added some “descriptive text” here. Text in the footer is the redirection link, and I marked it as a footer to separate it from the main section here. I used CSS to hide the text “footer” and add an image which will be clickable to the first page in the next steps. 3. Here is the survey’s first page: 4. Now, here you can add text. I added text but in italics to differentiate it. Giving CSS properties to the<i> tag (italic content) means it will be applied only here and nowhere else. You can use any other tag, too. If you want multiple images, you can add multiple tags and then style them accordingly in custom CSS. 5. Upload the images that you want to use here (under the custom icon). 6. Click on themes. You can do all customization under this page. 7. Under theme, you can get options to provide color to different elements of your survey form. 8. Below this color section, you will find the CSS section, where you can add your custom CSS. 9. In this step, I played with the HTML tags that I used on the thank you page. I gave them predefined height and width and set the required image as the background. Since it is just a tag and might contain text, I hid the text using CSS properties. 10. In the same way, I added a background image to the survey complete link URL using the CSS property on the tag (classes are pre-defined by CRM), so that the user can click and go back to the required page.  11. The survey link now shows both images properly, with the lower image clickable to bring the user back to the first page of the survey. Conclusion Although this is not a part of default customization of VoC, it is a very useful trick which I followed to improve customization of the VoC thank you to meet our client’s requirements

Introduction: XrmToolBox can be used to simplify many tasks. With so many tools now listed, a newcomer may wonder what others are using it for to maximum benefit. XrmToolBox is a Windows application that connects to Microsoft Dynamics 365 for Customer Engagement and Dynamics CRM, providing tools to ease customization and configuration tasks. It is shipped with more than 30 plugins to make administration, customization, and configuration tasks easier and less time consuming. In this article we will explore ten of our favorite XRMToolBox tools, exploring what they do and why they are so useful. How is it used? Documentation is available through the wiki of XrmToolBox Github’s repository. All the information regarding the prerequisites, connection, tools description, how to use is mentioned in the documentation. Ten useful tools of XrmToolBox: 1) Web Resource Manager Web Resource Manager helps to manage your web resources easily. This tool has saved hours of time for creating, updating and managing the web resources of Dynamics 365/CRM. This is a must have for all developers. 2) Ribbon Workbench The Ribbon Workbench tool helps to edit the Dynamics CRM ribbon or command bar from inside the XrmToolbox. By installing the Ribbon Workbench you’ll quickly be performing customizations that were previously only possible by time consuming and error-prone manual editing of RibbonDiff Xml. 3) Fetch XML Builder The tool is helpful for three major areas: Constructing FetchXML in ways that advanced find cannot Querying CRM for information not (easily) found in the CRM UI lie system and internal entities, hidden attributes or join on other fields Developer assistance like generating C# query expression code, OData query strings or composing queries for reports 4) Plugin Registration The Plugin Registration tool is an important tool used for registering plugins and custom workflows. 5) Auto Number Manager The Auto Number Manager tool’s primary goal is to give D365 customizers a way of managing auto number attributes. This feature was introduced with the 9.0 release. However, this release only supports creating and managing these attributes through the SDK. A user interface for the features is expected to be available from the 9.1 release of the platform. With the Auto Number Manager for XrmToolBox you can create, alter and delete these attributes through an easy to use UI. 6) Site Map Editor The Site Map Editor tool helps to manage the sitemap with no XML needed. Editing sitemap XML is scary for any developer, as any mistake in XML can make the entire CRM unusable. This tool helps to edit your sitemap components. You can easily create areas and subareas, update the order and copy or paste components from one area to another. You can also update all the sub area details like icons or titles for multiple languages. 7) Solution Component Mover The Solution Component Mover tool helps to transfer components from one or multiple source solutions to one target solution. It avoids components getting missed when creating a new solution or adding components from other solutions. Using this tool ensures you add all components from the selected solutions. 8) Metadata Document Generator Metadata Document Generator makes it easier for Dynamics CRM 2011 integrators to generate documentation about entities and attributes metadata. You’ll no longer have to write “by hand” these awful tables full of metadata information. This tool can connect to all type of Dynamics CRM 2011 deployments, including OSDP! 9) Bulk Delete tool The Bulk Delete tool has the ability to delete records from CRM based on system views, personal views, or custom FetchXML Queries. It also has the ability to edit a FetchXML query in the FetchXML Builder tool within XrmToolBox and to select the batch size and interval (in seconds) between batches. It takes less time to delete records as compared to traditional bulk delete from CRM. 10) Metadata Browser The Metadata Browser tool has ability to browse metadata from D365 CRM environment. This tool can be used to view all the metadata.  

Introduction: This blog explains how to set a default chart in a view’s Chart Pane Scenario: We have created custom chart on order named as Order by printing status. We want this chart should get open when user click on charts pane Steps: Go to Customization –> Order –> Charts. Click on More Actions –> Export Chart. .xml file will get download. Open that file with notepad. Search isdefault and set its value to true. Save Click on More Actions –> Import Chart Import the customized chart. Replace and Import Chart. Publish Customization. Now you can see that chart as default chart.

Introduction: In this blog we will be going through the steps of Error Handling in Microsoft Flows. Implementation: Step 1: We have created a basic flow that is triggered when a HTTP POST Request has be made to the generated URL. The body will contain a JSON array with some data The flow will then take the data passed in the POST request body and for each object in the JSON array, it create a record in Dynamics 365 Customer Engagement as shown below. In the above scenario  we pass the correct data, but in case the data that is passed to the URL is not correctly formatted or the data is missing we will encounter an error and the flow will fail. To handle such situations we will define an action that will take place when an error is encountered. Step 2: To Log the error, we will create another action to create a log error log in Dynamics 365 Customer Engagement.  To make sure that this is created only when an error is encountered we click on the Configure Run After option as  shown There are four options shown, here we select only the “has failed” option which states that the log will be created when there is a failure. Once this is done we can see the the flow shows a dotted red line for the last step, this is because the “Log Error in CRM” action will run only in one scenario i.e. when the above action has failed. The benefits of using this approach in our flows is that we can log all the errors at one place and also store the error response of the previous stage by simply selecting the Dynamic Content in the “Log Error in CRM” action.

Introduction: You might receive alert “The Team member position has already been filled” while submitting a request for an actual resource. Description: I was working on a project and we use PSA solution for resource management. Some Team Members was already added in project with “Generic Resource” and we wanted to replace resource with actual team member. But whenever I try to submit Resource request in PSA in “Project Team Member” I Receive alert message with “The Team member position has already been filled“. Solution: When you are adding a Project Team Member, are you choosing “Generic Resource” on Bookable Resource lookup for that team member? When you do this, you’re setting a Bookable Resource to team and thus can’t request for one anymore. When adding a Project Team Member, leave the Bookable Resource lookup unpopulated. This way a Bookable Resource is not assigned on the project team and you can submit a request against the created generic. When adding the Architect (Role), I have chosen Generic Demo Resource in the Bookable Resource lookup on the Quick Create. When adding the Consultant, I have left the Bookable Resource lookup unpopulated. Conclusion: So, this can be avoided if you are adding Resource from “Project Team member Associated view”.

Introduction: This blog details steps for Run Report button in UCI Form via Web Browser in D365 Sales. Scenario: Client requires Run Report button in UCI Form for Order Entity in D365 Sales Steps: Below are steps to be performed for enabling Report button on Order Entity Create WebResource with below javascript function. Create a button on Form and call function “PrintSalesOrderDetails”. Conclusion: Hope this blog helps you to run report in UCI browser.

Introduction: Dynamics 365 has two different type of form one is classic and other one is UCI. Now sometimes we want certain field to be visible on UCI and some on classic form. Description: We had a requirement where we wanted to show certain field on UCI, but it should be hidden on classic form. For example, signature field is not supported on classic form in Brower, but it works on UCI and tablet version. Here we wanted to hide the signature field on browser and it should work as it is in the UCI. Here is the code. We need to call this script on onload of the form function hideFieldonOrderWeb(executionContext) { debugger; var clientContext = Xrm.Utility.getGlobalContext().client; var device = clientContext.getFormFactor(); var formContext = executionContext.getFormContext(); var isUCIForm = isUCI(); if (isUCIForm == false && device == 1) { formContext.getControl(“cf_signature”).setVisible(false); } else { formContext.getControl(“cf_signature”).setVisible(true); } } function isUCI() { var globalContext = Xrm.Utility.getGlobalContext(); var appURL = globalContext.getCurrentAppUrl(); var ClientURL = globalContext.getClientUrl(); if (appURL !== ClientURL) { return true; } return false; } Explanation: We are checking form type and we are getting value as 1 which is same for both web and UCI. So we additionally need to check app type by using the code isUCI(). Value Form Factor 0 Unknown 1 Desktop 2 Tablet 3 Phone By this way you can hide the control. On UCI – Signature is visible On browser – Signature field is hidden

Introduction: In this blog we will use MS Flows to send out Surveys to customers once the Status Reason on the case is “Problem Resolved”. Implementation: Step 1: Below shown is the configuration of the flow. The flow is triggered once the Status Reason field in the case is changed. The statuscode is 5 which means “Problem Solved”. If problem is solved then we send a Survey form to the customer. Step 2: We then send an email to the customer as shown below We can also use the dynamic value by entering the “To” email id same as the one present on the Case. survey link details are mentioned in Step 3. Step 3: We have created a simple Survey using TypeForm once this is done a link will be created and the same can be entered in the Send email step. Then we add a step as shown below which will wait for the response . Firstly we sign in using own TypeForm account details and then Select the Survey from the dropdown and fill in the details as shown below. Once the response is received we have added a step to update the User details who was working on the case. We can create a custom field to store the responses received from the TypeForm step. Conclusion: This is useful to as we can improve customer service by easily by using MS Flows. We can also use Microsoft Forms, SurveyMonkey to create surveys and get responses

Introduction: In this blog we will discuss how we can solve XML issue while importing solution from one environment to other. Scenario and Steps: 1. Deploying a solution from one environment to other causing issues below issue. This error occurs when there are some integrations enabled for your entity. 2. Click on “Help me resolve this issue” and a Dialog will be opened which shows the specific error. As you can see element “IsMSTeamsIntegrationEnabled” is present in the solution which is not present in target solution. Thus we will remove this element from XML and import the solution. 3. To remove the element from XML follow the below steps: Extract the solution you want to import. Open customizations.xml file. Remove “isMSTeamsIntegartionEnabled” element from XML and save the XML. Zip all the files and import the solution to your environment. Your solution will be imported to the targeted environment.

Introduction: Dynamics 365 service team regularly sends email notifications to the administrators in your dynamics 365 organization. Now with simple mail box rule, you have complete control who should receive the mail. Description: As an administrator you can setup the mail box rule to automatically redirect email communications from dynamics 365 to additional recipients. People outside of your Dynamics 365 organization, such as your partners. People inside and outside of your company. Send email notifications to multiple recipients: By default, admin will receive the email notification but if you want to change the email notification to some other user. follow the below steps: 1. Sign in to portal https://portal.office.com. 2. On the Office 365 menu bar, click Admin centers > Dynamics 365 > Instances tab. 3. Choose an instance that has notifications you want to change. 4. Click Notifications. 5. Enter the email addresses of people to receive update notifications for the selected instance and click Save.