Introduction: Sometime there is a need to know when and who imported the solution in to CRM. This will be done by XrmToolBox plugin called “Solution History”. Purpose of Solution History: The purpose of the tool is to view a historical list of solutions that have been imported. This provides sort of audit functionality for solutions, as the OOB solution view doesn’t really display how many times a solution has been imported, version number that was updated, error/warning messages that were encountered during solution import. Steps: Install Solution History plugin from Plugin Store in XrmToolBox. Open the plugin and connect to the environment. Select the time frame for the solution. The solutions will be displayed as below. Select the solution for which you want to check the details. Click on Load Solution History. The details will be shown as highlighted below. Other methods of knowing this are listed below: 1) Looking in to the database 2) Checking XML Hope this helps!!

Introduction We had developed a functionality for Dynamics CRM v8.2 on Quote Entity by adding a custom button and on clicking a button we run a report, capture its contents using JavaScript, convert it to a PDF and attach the PDF to an Email Record. Below shown is the code snippet quoteInvoice = { runReportToPrint: function () { debugger; var params = quoteInvoice.getReportingSession(); var newPth = Xrm.Page.context.getClientUrl() + “/Reserved.ReportViewerWebControl.axd?ReportSession=” + params[0] + “&Culture=1033&CultureOverrides=True&UICulture=1033&UICultureOverrides=True&ReportStack=1&ControlID=” + params[1] + “&OpType=Export&FileName=public&ContentDisposition=OnlyHtmlInline&Format=PDF”; //Calling the below function converts the report to PDF format. quoteInvoice.convertResponseToPDF(newPth); }, getReportingSession: function () { var selectedIds = Xrm.Page.data.entity.getId(); selectedIds = selectedIds.replace(‘{‘, ”).replace(‘}’, ”); var strParameterXML = “<fetch distinct=’false’ mapping=’logical’ output-format=’xml-platform’ version=’1.0′><entity name= ‘quote’><all-attributes/><filter type=’and’><condition attribute=’quoteid’ value='” + selectedIds + “‘ operator=’eq’ /></filter></entity ></fetch >”; var reportGuid = “DAF05843-CA33-E711-811E-FC15B42827EC”; var reportName = “Quote Invoice.rdl”; var pth = Xrm.Page.context.getClientUrl() + “/CRMReports/rsviewer/QuirksReportViewer.aspx”; var retrieveEntityReq = new XMLHttpRequest(); retrieveEntityReq.open(“POST”, pth, false); retrieveEntityReq.setRequestHeader(“Accept”, “*/*”); retrieveEntityReq.setRequestHeader(“Content-Type”, “application/x-www-form-urlencoded”); retrieveEntityReq.send(“id=%7B” + reportGuid + “%7D&uniquename=” + Xrm.Page.context.getOrgUniqueName() + “&iscustomreport=true&reportnameonsrs=&reportName=” + reportName + “&isScheduledReport=false&p:quoteid=” + strParameterXML); var x = retrieveEntityReq.responseText.lastIndexOf(“ReportSession=”); var y = retrieveEntityReq.responseText.lastIndexOf(“ControlID=”); var ret = new Array(); ret[0] = retrieveEntityReq.responseText.substr(x + 14, 24); ret[1] = retrieveEntityReq.responseText.substr(x + 10, 32); return ret; } } The runReportToPrint() function is called when the custom button is clicked Issue and Error Details Once the environment was upgraded to V9.0 we were facing issues as the PDF that was generated was corrupted as show below. While debugging the code we got the following message. On further research we found that the URL has been changed and  below shown is the new path that has to be used which works correctly on V9.0. var pth = Xrm.Page.context.getClientUrl() + “/CRMReports/rsviewer/ReportViewer.aspx”; Once this change was done  we did not get any error and the PDF of the report that was generated opened correctly with all of  its contents.

Introduction: A “shared shift” configuration lets retailers have a single shift across multiple registers, cash drawers, and users. A shared shift has a single starting amount and a single closing amount that are summarized across all cash drawers. Shared shifts are most typical when mobile devices are used. In this scenario, a separate cash drawer isn’t reserved for each register. Instead, all registers can share one cash drawer. Steps to Configure: Go to Retail –> Channel setup –> POS setup –>POS profile –> Hardware profile –> Drawer –>Enable shared shift option. Go to Retail –> Workers–> Select the user and go to retail tab. Go to POS Permission and select the appropriate permission group and assign it to the user. Make sure that the  user must have “Allow manage shared shift and Allow use shared shift” permissions enabled Save the changes Go to Distribution Schedule and run the job for Register and Staff. Note: Only one shared shift can be opened at a time in each store.

Introduction: In this blog I’ll be demonstrating few features of Business Central October Release[RC3]. Pre-requisite: Microsoft Dynamics 365 Business Central October Release[RC3]. Demonstration: 1.Refreshed User Experience Improved Card Page Layout. Improved List Page Categorized Actions. Changed position of New,Edit, Delete as well as Previous andNext buttons. 2. Improved Productivity Advanced filtering with multiple column filtering: Limit Totals: Row-based column copy past: Actual Data: Data in Excel Keyboard shortcuts: The October release, also consists the shortcut F8 that copies the value of the cell above. Thus, you can fill the new rows by moving across cells and selecting F8 on the cells where you want to copy the values from cell above. List of Keyboard Shortcuts : https://docs.microsoft.com/en-us/dynamics365/business-central/keyboard-shortcuts 3. Improved Search The search option has also been enhanced and categorized where previous search results were only related to pages and reports. In the upcoming release with the improvement in logic, the search results will also include the actions on the current page and the documentation along with the reports and pages. From the search itself you can check and perform the tasks that you want (for example: Create a contact for customer) Enter the contact details for the customer and click on OK 4. Permission Sets are Editable In Business Central October Release, the Permission Sets are Editable. New Permission Sets can be created as well as Permission Sets can be modified and also indented as well. Click on More Options to get the details. Changing the Permisison Sets in Business Central: Added an execute permission: Conclusion: These are few features of the Business Central. In the next blog I’ll demonstrate about the AL Language extension improvements.

Introduction: This blog details steps for Run Report button on Project Entity in D365 PSA. Pre-requisites: 1. Ribbon Customizations solution installed in environment. Steps: Below are steps to configure Company Insights on custom form “FSA Account” for Account Entity 1. Create a new solution for Ribbon Customizations. Add project entity in the solution. 2. Add Another entity which has Reporting Enabled like – “Opportunity”. 3. Open the new solution in Ribbon Work bench. 4. Copy the “Report” button from Opportunity. 5. Paste the Button on Project Form Ribbon like below: 6. Publish the ribbon Customizations. 7. You should now be able to see the Run Report Button on Project form. 8. Similarly you can also add other buttons like “Run Workflow” or “Start Dialog” button on Project or any other entity which does not have this enabled by Default. Conclusion: Hope this blogs helps you to enable “Run Report”, “Run Workflow” or “Start Dialog” button missing from Project entity in D365 PSA.

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: Item Cross reference is useful to quickly identify the items that were ordered by a customer or that you are purchasing from a vendor on the basis of item numbers other than your company. You can use Item Cross reference on Purchase Order, Sales Order, Purchase Quote and Sales Quote Steps: Following are steps to setup Item cross reference. Open the Item list Click on edit button to Open Item Card. In Navigate tab click on Cross References button. Select Vendor, Customer or Bar Code in the Cross-Reference field. In the Cross-Reference Type No. field, select Vendor No, Customer No. or Bar Code Enter Vendor, Customer Item No. or Bar code no in the Cross-Reference No. field. Enter Unit of Measure Enter description for the Item. This description will be automatically copied in Purchase or Sales order line when you enter cross reference in Sales or Purchase order line Create a new Purchase Order/ Sales order. By default, the Cross-Reference No. field is not shown in the Order Line. Use Personalization and add it. In Cross-Reference No. field to select a cross reference no. System will automatically fill the Item No. and other information in the order line.

Introduction: Work Hours mentioned under a User/Bookable Resource aren’t the same as they show. Ever wondered what is Cross Day on Work Hours for a Bookable Resources in Dynamics 365 PSA or Field Service? Or even User record for that matter? And why not the actual Work Hours a resource is set to? You should see this – instead of this – Reasoning: So, The Bookable Resource’s time zone is GMT. And so is the same time zone of the logged in user i.e. GMT. In that case, you’ll see the actual time set for the user i.e. 8am to 5pm. But, let’s say, you are in a different time zone – Sydney, for example. And you are viewing Work Hours for a Bookable Resource who was set in some other time zone, their time conversion to your time will result in “crossing the day” over and hence, you see “Cross Day”.

Scenario: We had created the custom Business Process Flow on order entity which was visible on web client but not in UCI. For making it visible in UCI we must add that Business Process Flow in App. Steps: Create new solution and add Existing App which you are using in that solution. Add Custom Business Process Flow in App. Validate Save and Close. Publish All Customization.

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