Introduction: In this article, we will learn how to set a default dashboard when you login to Power BI Service. Default Dashboard is termed as ‘Featured Dashboard’ in Power BI. Steps for configuring featured dashboard: Login to Power BI Service Open the Dashboard you need to display when you open Power BI Service. Click ‘Set as featured’ on the top navigation bar of your dashboard. A Pop-up window will appear for confirmation. Click on ‘Set as featured dashboard’ button. 1

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: In Business Central, the existing reports cannot be modified. Thus, for modifications in the report, the existing report is to converted to text using Text-To-Al and then modifications are to performed. But in case of Check Report(10401) it doesn’t work giving error ‘Index out of bounds!’. Pre-requisite: Microsoft Dynamics Business Central (Online) Solution: When modifying the Check Report in Business Central, the only approach available is converting existing Check Report 10401 to Text and then using Text-To-Al.Which gives the error ‘Index-Out-of-Bounds!’. Thus for a workaround I used the code from https://community.dynamics.com/nav/b/moxie4nav/archive/2014/12/08/numbers-to-words Although this algorithm works perfectly on NAV and Business Central On Premise, it returns the same error on Business Central Online. As assumed, it was because of the recursion used. So, here is the non-recursive algorithm that works perfectly fine up to 8 digits characteristics and 2 digits of mantissa. List of variables: Units[10], Tens[20], Expos[30] are arrays with respective dimensions. Initialization of Variables: Code: Kindly find the text object on GitHub: https://github.com/olisterrcf/CheckReportAmountInWords Conclusion: While the updates are still getting generated on this issue, it is far from being conclusive to reach out to the expected results. As per our cordial discussions with Microsoft, the existing  report objects on On-Premise versions such as NAV and Business Central On Premise are not 100% compatible with Business Central Online  which are converted using Text-To-Al tool. In the next blog, I’ll write about update for the same.

Introduction: We all have noticed Send Approval Request button on Vendor and Customer pages. You can select Customer workflow from the workflow template Sales and Marketing. Vendor  can be configured similar to customer workflow. These standard workflows can be enabled from the workflow page….but what’s the use of it? why do we need it? This blog explains the use of Vendor, Customer workflow in Dynamics NAV. Pre-requisites: Microsoft Dynamics NAV 2016. Steps: 1. Enable the Vendor, Customer, Item workflow: Browse to workflows and select new workflow from Template and under the Sales and Marketing select Customer Approval workflow. In the workflow response select the workflow user group or direct approver to which approval will be sent. Similarly, configure Item and Vendor workflow. 2. Send the Customer for Approval: In the Customer Card page click on Send approval request to sent the customer for approval. Once approval is sent. Workflow Factbox appears on the right hand side. 3. Use of the workflow: Customer Workflow Now this workflow is sent for approval but not approved. If you navigate to sales order and use the same Customer. If you post the sales order or Journal, you will get the below error. Once the customer is approved, Sales order is approved successfully. Vendor Workflow: Send the Vendor for approval by clicking on Send approval request. Workflow factbox is visible. Now when you post the Purchase order or  journal for account type Vendor you will get the below error. Once its approved, The journal lines is posted.

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: With Azure AD Conditional Access, you can control how authorized users’ can access your cloud applications. In this article, we will see how to create conditional access to enforce MFA, if the user is accessing services from the untrusted location (outside of the company’s network). Multi-factor authentication (MFA) is a method of authentication that requires more than one verification method and adds a second layer of security to sign-ins. Requirement: I had a requirement from a client to prompt for MFA if a user is trying to access Dynamics 365 (or other O365 services) from a location outside of company network. Pre-requisites: You will require Azure AD Premium license for users. Create a security group and add the users’ you need to specify in the policy. Company’s public static IP in CIDR format. Example – 15.250.0.89/24 (You can contact your network team to get this detail) Trusted locations: Configure MFA trusted IP’s in Azure AD (see below image). Provide your company’s public static IP in CIDR format (check below image). Conditional Access: Go to Azure AD > Conditional Access > +New Policy Name the policy as UntrustedLocation_PromptMFA and the first thing to configure is Assignments in which you need to mention the User & Groups to be included in this policy (see below image). Select Dynamics CRM Online under Cloud Apps. You can similarly choose other applications as well (see below image) Under Conditions, you need to configure the Device state and client apps as per your requirements (see below images). In Location: Include – Any locations Exclude: Selected locations and then select MFA trusted IPs (see below image) In Access control > Grant Access, tick Require multi-factor authentication (see below image) Finally, Enable the policy and Save. User specified in the group will be asked for MFA when accessing Office 365 services from an untrusted location (outside the company’s network). Conclusion: In this way, we can enforce MFA when Office 365 services are accessed from untrusted locations.

Introduction: Recently, we encountered an issue while exporting the SSRS Reports to Excel. In CRM, the SSRS Report was displaying the data correctly but for few filter criteria, we were not able to export the Reports to Excel.  On troubleshooting in SQL Data Tools, we found that it was throwing the below error. Error Details: The row item structure object corresponding to a line cannot be null. Reason for the error: We had 2 matrix in our Report one of which had data and another was retrieving no rows according to few criteria. Whenever a matrix is null, you cannot export the Report to Excel as Excel does not render null matrix. Solution: Add a visibility condition on the matrix that if the dataset pertaining to the matrix returns no rows then hide the table. Voila! You are good to go. Happy Reporting!!