Introduction: Working with D365 is best when you’re trying to use as much OOB stuff as possible. Simplest configurations like selecting a view for your Lookup field is easily possible on the D365 Form. However, this is not possible on the fields on the Business Process Flow Use of addPreSearch() and addCustomFilter() on BPF Fields: Now, since you have this field on the BPF and want to add filter to Lookup records, you’ll need to use JS customization to achieve this and add your filter’s criteria in the code to show results as expected. Let’s say you see all the lookup records on the field on the BPF 2. I want to see only Semi Annually type of Plans on the Lead. And I can’t simply do this from the Field’s Properties like on the form. Because, it’s not available. 3. Hence, I’ll write JS code as follows to achieve this: // JavaScript source code var oOFFormCustomization = { preFiltering: function () { “use strict”; if (Xrm.Page.getControl(“header_process_cf_defaultplan”) != null) { Xrm.Page.getControl(“header_process_cf_defaultplan”).addPreSearch(oOFFormCustomization.preSearchProductFamily); } else return; }, preSearchProductFamily: function () { “use strict”; var fetchQuery = ‘<filter type=”and”>  <condition attribute=”cf_plantype” operator=”eq” value=”979570001″ /><condition attribute=”statecode” operator=”eq” value=”0″ /></filter>’; Xrm.Page.getControl(“header_process_cf_defaultplan”).addCustomFilter(fetchQuery); } }; 4. And I register the method on Page Load of the Form. 5. And I see these results once it successfully filters!

Introduction: This is an observation I made when one of our clients wanted to have a limit on the calculated fields. Let’s say, a lower limit of the currency field that is expected to throw an error (or somehow not allow) the currency going in negative values for a calculated field. Observation: Now, I want to keep the Minimum Value as $0. I’ll keep the Minimum value as 0 so that when I can make it as Calculated Field, the Minimum Value gets locked by $0 I’ve entered. See screenshot below: But, as soon as I make it as Calculated Field and click on Save, this happens- It still appears that I will save it as 0 But, it creates the field, locks the minimum field and then defaults it back to the original minimum value. Bottom line: We cannot have our own Minimum Value on the Calculated Currency fields. But however, I found that this is allowed for other calculated fields. Like the Whole Number.

Introduction: Field Service in PSA uses Incident Types. Incident Types can be defined to showcase what are the most common scenarios for field works on a particular Work Order. Having generic tasks, skillsets defined for an Incident Type saves the effort to re-enter the iterative information on a WO. Setting Up Incident Types: Field Service Incident Types can be defined in FS Administration area as shown below: Assuming I’m a branded furniture reseller, most common tasks for my technicians on field is assembling wooden furniture like Beds, Cupboards, Tables etc. So, I’ll create a generic Incident Type called as Furniture Assembly. What all to enter in Incident Types 1. Incident Types has first important section called as Characteristics. Meaning, any resource with that Skillset is required to be performing this WO. In my example, I want the carpenter to be Proficient in using Sawing and Drilling. 2. Next, is the Details In this section, Estimated Duration is automatically calculated based on the Service Tasks (point no. 3 below) to be performed by the resource and what should be the Default Work Order type. Note: Once when Default Work Order Type is selected, if you select the Primary Incident Type on the WO, the Work Order Type is automatically picked in the Work Order you are creating. 3. Service Tasks is the next section where you can list what common tasks should be performed by the resource on field. With the Estimated Duration entered, they drive the Estimated Duration on the Incident Type itself. 4. Products section is next where you can enter the Products that will be used by the field service agent in order to perform their required task. Products can be Inventory, Non-Inventory depending on their use. 5. Services are what field service agents will provide to the customers and might charge for it. Products of type Services can be entered here. Adding Details to the Work Order: Once your Incident Types are set up, you can use them in your WO and get all the data in the WO itself! You can choose to override any data from it if you want. Create a WO and fill out the common details. Then, select the Primary Incident Type as the one you selected. And when you select it, you’ll see the WO type has been automatically populated. And once you save, details from the WO like the Characteristics, Incidents, Service Tasks, Services and Products have been auto-populated. This makes things a lot easier!

Overview: Often you miss doing your time entries in PSA for the work done and go on a leave! You either then need to just struggle to find a system and do it yourself or raise some other kind of request to make sure billing is done right. But, you can delegate time entries to a colleague and it is all taken care of. Assigning Delegates in PSA: In Project Service, you can see the entity Delegates. In this entity, all you need to do is create a Delegate record as shown below You can either delegate a fellow resource for Time Entries or for the Expense entries. In this case, I’ll let Somesh make Time Entries on my behalf and hence make him my Delegate in PSA for a week on which I’m on PTO. Entering Time Entries as Delegates: Now, looking at Somesh’s angle, if he has needs to make time entries on my behalf. He would need to go to Time Entries, then he will need to look at the ribbon for his name and change the user to Priyesh Wagh. Once the other user is selected, their Timesheet appears and all the time entries by the other user appear. Here, Somesh can make time entries just as he would usually do for himself and they would actually be registered for the Resource Priyesh Wagh.

Overview: Often, we wonder what could be wrong where we see a generic error on Documents in Dynamics 365. Something like this – That’s when you wonder if all the privileges in D365 Security Roles for SharePoint Site or Document entity are correct or not? In fact, it’s the SharePoint privileges that you must look into. Privileges On SharePoint: Even if the error indicates that you don’t have access in D365, it is actually the SharePoint site that’s missing permissions. Here’ where you need to check for the O365 User’s SharePoint privileges: Navigate to SharePoint Admin Center in the Office 365 Admin center Next, in any of the intended SharePoint sites, navigate to the Gear Icon and then Site Settings. In Site Settings, navigate to People and groups under Users and Permissions area. Check that you might not have the intended user in that list. You can then click on Add and add the user in the list. You can either add an individual user or ‘Everyone Except external users’. and confirm that you see them in the list now. Confirm Permissions: Now, you can ask the users to check and they should be good to go. Hope this helps!

Overview: Here’s a quick helpful control to enter barcodes in D365 fields. Here is how it goes – Adding Barcode Control: Here’s how you can add the Barcode Control. Select Add Control in the Field Property section. Select Barcode Scanner and click on Add. Select the appropriate configuration of devices for the control and click OK Finally, save and publish your customization. Seeing it Work: Now, since I have published a field called Brochure Barcode. I can use the same on the mobile device to capture barcodes without having to type them manually I can see the icon on the right end of the text box of type Barcode. On clicking the barcode icon, my phone’s camera opens. Show it in front of the barcode. And it automatically detects and enters the same in the textbox. That’s it. Hope this helps!

Overview: Auto Scheduling in PSA’s WBS books the hours when you enter the dates and dates when you enter the hours. They are interlocked. I want to schedule a task which is less in no. of hours but will span across more than expected duration of period. Such requirement is when signing a support contract with the client. Scenario While defining WBS for a Project called Abby’s D365 Implementation. I want to schedule a UAT task to span across over 10 which has only 22 hours. If I select the days as 3, I get my 22 Hours. Or select hours as 22, I get 3 days. But then, I can’t change the same to extend for more days. If I select the desired 10 days, I get 80 hours.Hence, I’ll toggle the Task Mode to Manual. Now, I can keep my Effort Hours and Duration as desired. To represent Manual mode, the icon changes to Calendar with a Pencil on it. That’s how you can keep flexible hours for the tasks you want to expand over a long duration.

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: 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.

Overview: Often while working on PS, I was struggling to  get the Chargeability View right. The main reason is not having the right Price List setup at the right places. There are 4 important places where the Price Lists need to be setup properly. Product Catalog with Role Prices having Org Unit A Account having corresponding Sales Price List and the same Sales Price List under it’s Project Price Lists grid. Opportunity having Org Unit A as Contracting Unit and Product Price list having Sales Price List for Org Unit A selected. Quote derived from the Opportunity having the same Account, Opportunity, Contracting unit and Product Price List selected. Organization Unit: For each Organization Unit you add to PSA, make sure you’ve added a Cost Price list to the Organization Unit as well as a Sales Price list exists for the same. Make sure Organization Units on the Role Prices are selected correctly on both the Sales and Cost Price Lists Sales Price List on Account and Opportunity: Account and Opportunity too should have the same Sales Price list whose Cost Price list is associated with the Organization Unit of the Account’s and Opportunity’s Organization Unit. Make sure you’ve correct Organization Unit and Product Price List as a Sales Price List for that Org Unit selected on the Opportunity form. Chargeability View on Quote Lines: Once everything flows from Account to Opportunity to Quote and to Quote Lines, you can see that your Chargeability View pops-up properly. Hope this helps you derive correct Chargeability View without hassle.