Introduction: I faced an issue recently where I was trying to print a report directly to printer but Print Management Settings didn’t show any Printers option. In AX 2012 we had to perform setup in AX 2012 Server Configuration to print documents or report to connected printers. In Dynamics 365 for Finance and Operations, Enterprise Edition you need to install and setup Document Routing Agent in your system and activate Network Printers in D3FOE for printing. Steps: Install Document Routing Agent. Setup Printers in Document Routing Agent. Manage Network Printers in D3FOE. 1. Install Document Routing Agent. Go to Organization Administrator -> Setup -> Network Printers In Action Pane, Go to Application -> Download document routing agent installer Install downloaded setup file ‘DocumentRoutingAgentSetup’. 2. Setup Printers in Document Routing Agent. Go to Settings and enter details. Click OK. Application Id – Unique Appication Id. It  is filled automatically. Dynamics 365 URL – URL of D3FOE Azure AD Tenant – Domain name of Azure Active Directory Run as Windows Service – This will configure agent as a windows service. If you want to print custom size reports then agent should be desktop app as it sends report to Printers with help of Adobe Reader instead of sending it to Target folder. Agent as service will send it to Target folder. Sign In with your logic credentials. Go to Printers. You can see the installed Printers on your device. Select the Printers you want to enable for printing in Operations. 3. Manage Network Printers in D3FOE. Go to Organization Administrator -> Setup -> Network Printers. You will see the list of Printers enabled on Document Routing Agent. Enable the printers by setting Yes for Active field. Conclusion: Once the setup is completed you can use the Network Printers from Print Destination – Printers option. Agent once installed on one machine and enabled as Network Printers can be used by anyone using the D365 Operations.

Introduction: Quantity adjust functionality is useful to adjust the Quantity of Inventory from ‘On hand inventory’ form. Steps: Navigate to Product Information management > Products > Released Product In released Product form, select the product for which you want to adjust the Quantity. On Manage Inventory action tab, click on ‘On Hand inventory’ button. On ‘On Hand inventory’ you can check available quantity. Click on Quantity adjustment button to adjust the quantity. On Counting form, select Inventory dimensions, tracking dimensions which are required. In Quantity field, specify the quantity. you can decrease the quantity by specifying it into negative and increase the quantity by specifying it into positive. Once quantity has been specified click on OK button. Now you can check adjusted quantity on ‘On Hand Inventory’ form. Conclusion: By using Quantity adjustment functionality, you can directly adjust inventory quantity on ‘On Hand Quantity’ form without using counting journal, Inventory adjustment journals.

Introduction: When Copying a database between environments, you will need to run the Environment Re-Provisioning tool before the copied Database is fully functional, to ensure that all the Retail Components are up-to date. Steps: Steps to Process Re-Provisioning Tool: 1. Log into your LCS Project. 2. Go to Asset Library. 3. Select “Software Deployment Package”. 4. Click on Import. 5. Select “Environment Provisioning Tool”. 6. Click Pick. 7. Once this Package is available in your Asset Library, Upload this package to your system and schedule it to run as you do for any other deployable package. 8. Go to Maintain and Apply updates.

Overview Xrm.Panel is a new additional to the client-side scripting in Dynamics 365. This feature is still in preview in the D365 December 2016 update. Panel is a simple static place on your D365 web client which loads a Web Page inside it. Perhaps, the best use of the same could be a Web Chat application implementation. Implementation Simple – I’ve made a JS Web Resource that has a function to call the Xrm.Panel.loadPanel(url, title); method and I’ve invoked the same on change of a Phone Number. Here’s a simple JS snippet I’ve written: oAccountCustomization = { loadPanel: function() { “use strict”; Xrm.Panel.loadPanel(“https://cft89.crm.dynamics.com//WebResources/new_SamplePage”, “Hello”); } }; And redirected it to another HTML page in my own D365. Then, I’ve added this to the onChange of the PhoneNumber on the Account record. And saved and Published the customization. Seeing it work: Now, when I change the Phone Number field on the Account, the slider appears on the right hand side of the page. You can click on the arrow to bring it in focus. Here we go! The Panel is now seen. Remember, this works only on the Web Client.

Introduction: This blog consists of information on how you can find the users having specific privileges and in which role they have the privileges. Solution: Make use of the below Fetch XML to identify who has access to prvReadAccount related to his Role. The fetch can be performed on System User level or for teams. <fetch version=”1.0″ output-format=”xml-platform” mapping=”logical” distinct=”false” > <entity name=”privilege” > <attribute name=”name” /> <link-entity name=”roleprivileges” from=”privilegeid” to=”privilegeid” alias=”pu” link-type=”inner” > <link-entity name=”role” from=”roleid” to=”roleid” alias=”rpu” link-type=”inner” > <attribute name=”name” /> <link-entity name=”systemuserroles” from=”roleid” to=”roleid” alias=”sr” link-type=”inner” > <link-entity name=”systemuser” from=”systemuserid” to=”systemuserid” alias=”srr” link-type=”inner” > <attribute name=”systemuserid” /> <attribute name=”fullname” /> </link-entity> </link-entity> </link-entity> </link-entity> <filter type=”and” > <condition attribute=”name” operator=”eq” value=”prvReadAccount” /> </filter> </entity> </fetch> Response: <fetch version=”1.0″ output-format=”xml-platform” mapping=”logical” distinct=”false” > <entity name=”privilege” > <attribute name=”name” /> <link-entity name=”roleprivileges” from=”privilegeid” to=”privilegeid” alias=”pt” link-type=”inner” > <link-entity name=”role” from=”roleid” to=”roleid” alias=”rpt” link-type=”inner” > <attribute name=”name” /> <link-entity name=”teamroles” from=”roleid” to=”roleid” alias=”tr” link-type=”inner” > <link-entity name=”team” from=”teamid” to=”teamid” alias=”trr” link-type=”inner” > <attribute name=”teamid” /> <attribute name=”name” /> </link-entity> </link-entity> </link-entity> </link-entity> <filter type=”and” > <condition attribute=”name” operator=”eq” value=”prvReadAccount” /> </filter> </entity> </fetch>

Introduction: In the current 8.2 version of D365 PSA, we can only Hard Book a Resource from the Project Team Member View whereas in the v9.0, we can Soft Book from the Project Team Member View from with a few extra clicks. v8.2 – Current There is a button called Hard Book which lets you Hard Book the resource selected as shown below Then, you can plainly Hard Book the resource. v9.0 There is a generic option called as Book in the Project Team Member Associated View On clicking the same, a separate window opens with the selected Resource to Book them Conclusion Soft Booking from Project Team Members Associated View is not possible in v8.2 but is possible in the v9.0 version.

Introduction: In this blog article, we will see how we can increase simultaneous remote logins for multiple users to a remote connection. This will create different sessions for each login. It is important that we don’t increase simultaneous connection more then required as performance can decrease due to more resource demand for each login. Steps: Run -> gpedit.msc -> enter Administrative Templates -> windows Component -> Remote Desktop Services -> remote desktop session host -> connections Go to Restrict Remote Desktop Services users to a single Remote Desktop Services Session Select Disabled. Click OK Go to Limit number of connections. Select Enabled. Change ‘RD Maximum connections allowed’ to the desired connection allowed.   This will enable 2 simultaneous logins for Remote connection. In case Remote Desktop session host is not installed maximum connections allowed for remote login is 2.

Introduction: The purpose of this article is to help fellow entrepreneurs and sales managers leverage the power of Office 365 and Dynamics 365 to manage and build their sales pipeline with a few easy steps. In this article, we focus on utilizing Business Process Flows on Opportunities in Dynamics 365 and Triggering Email Notifications to team members. Step 1 – Enable the Out of the box Opportunity Sales Process In case you are not using Business Process Flows, please start using it. For a growing Sales team, using Business Process Flows on Opportunities enables a methodical approach to your pipeline management. When you enable the out of the box Opportunity Sales Process, you will see the following Process Flow appear on your Opportunities – The above Business Process Flow has 4 stages – Qualify, Develop, Propose and Close. You can move your Opportunity through each of the stages as you make progress. When the Opportunity reaches the proposal stage, we mark the Present Proposal check box as ‘complete’ as per below – We also ensure that we save the proposal on the Opportunity at that point – Step 2 – Send Email Notification to Project Delivery Manager on Proposal Complete When a proposal is sent to the Customer, we trigger a workflow notification to our HR and Delivery Managers. The Workflow email looks something like this – The above email serves as a reminder to our Delivery Manager that a new Project might be coming their way soon. It also informs our HR Manager, so they can look at our PowerBI Resource Allocation Dashboards to understand staffing and hiring needs. In addition, we also include the URL to the Opportunity, so our Delivery Manager can look at the Opportunity and even the proposal that we attached to the Opportunity. Finally, when an Opportunity is Won, we send a similar workflow email. Hence the ‘Propose’ stage email provides our Delivery Manager with some preparation time to ensure we are ready for Kick off when we Win the Opportunity.  Step 3 – Just do it. Yes, this step is same as in my previous article. Get in the habit of doing this and it will help close the communication loop from Sales to Delivery to HR, thus helping your organization meet its commitments. Remember… ‘Sales cures all.’ Let’s take care of that sales pipeline.’ You can always email me at AShah@CloudFronts.com to discuss your sales processes and technology adoption. In the coming articles, I will continue to focus on efficient ways to build and manage your sales pipeline and how this ties into one of the most important KPIs for running your professional services business.

Introduction: This blog explains how to Integrate PowerApps with Dynamics 365. Keep the following restrictions in mind: Only PowerApps users in the same tenant can access the embedded app. To access PowerApps using Internet Explorer 11, you must turn off Compatibility View. Steps to be followed: In powerapps.com, on the Apps tab, click or tap the ellipsis ( . . . ), then Details. Copy the App ID. Substitute the [App ID]value in the URI.: https://web.powerapps.com/webplayer/iframeapp?hideNavBar=true&source=iframe&appId=/providers/Microsoft.PowerApps/apps/579938ff-e1a0-4891-a8b9-8d69c103fd84 Embed your app in a website: Embedding your app is now as simple as adding the iframe to the HTML code for your site.http://<iframe width=”[W]” height=”[H]” src=”https://web.powerapps.com/webplayer/iframeapp?hideNavBar=true& source=website&screenColor=rgba(165,34,55,1)&appId=/providers/Microsoft.PowerApps/apps/[AppID]”/> To add PowerApp inside CRM  as web resource: Keep the following points in mind for authenticating users of your app: If your website uses Azure Active Directory (AAD) based authentication, no additional sign-in is required. If your website uses any other sign-in mechanism or is not authenticated, your users see a sign-in prompt on the iframe. After they sign-in, they will be able to run the app as long as the author of the app has shared it with them Steps: Specify the width and height for App. Specify the app id. Sample HTML code: <!DOCTYPE html> <html>  <head> <title>HTML Iframes</title> </head> <body> <p>App Goes here…</p> <iframe width=”250″ height=”250″ src=”https://web.powerapps.com/webplayer/iframeapp?hideNavBar=true&source=website&screenColor=rgba(165,34,55,1)&appId=/providers/Microsoft.PowerApps/apps/579938ff-e1a0-4891-a8b9-8d69c103fd84″ /> </body> </html>  

Overview: In this blog we will see how we can prepopulate lookup and dropdown (option set) fields on an Entity form in D365 CRM Portals using JS. Pre-Requisites: D365 CRM Portals D365 CRM Environment Introduction We know that if we want to prepopulate a lookup or a dropdown field on a form in CRM Portals the best method is to use Entity Form Metadata. But there is an alternative way to prepopulate the Lookup and dropdown (Option set) fields on an Entity form in D365 CRM Portals using JS. Scenario: To implement the functionality of prepopulating a lookup field we will be using the account lookup field on the CRM entity form based on the value entered in the contact field for a created opportunity in the partner portal. For the prepopulating the dropdown field we will be using the opportunity status field. Process: First of most we will see how to prepopulate the lookup field on the entity form based on the value entered in another field. As mentioned in the above scenario we need to prepopulate an account field on an opportunity form based on the value present in the contact field. To insert a value into a lookup field using JS(jquery) we need the following information as mentioned below. The field value to be displayed. For eg. Account full name. The GUID if the record to be displayed. For eg. GUID of the account record. The logical name of the entity. For eg. Logical name of the account entity. Now we will see how to get these details form the existing information we have on the opportunity form. When we open an opportunity record, on the details page in the URL section we get the id of the opportunity record as shown below We will insert this id into the fetch xml using liquid template to obtain details of the contact related to the following opportunity record as shown below. As shown above we have used the opportunity id in the fetchxml to get the contact details. Once we have obtained the contact details from which we will be using the contact name value in the next fetchxml to get the related account information. In the following below shown fetchxml we will get the value and the id of the account record to be inserted. Once we get the account record details we will write the jquery in the following manner to insert the value into the lookup field. Jquery syntax: <script> $(“form_attributeid_name”).val(“record_value”); $(“form_attributeid”).val(“record_GUID”); $(“form_attributeid_entityname”).val(“entity_logicalname”); </script> Once we publish the liquid code we will see that the account field on the opportunity form is prepopulated with the value related to the value present in the contact field. For prepopulating the dropdown(option set) field we need the option set value of the record to be displayed. To set the value in the option set we will write the following jquery. $(form_attributeid).val(“attribute_optionsetvalue”); Hope you all find this blog helpful. Happy coding in CRM portals.