Introduction: In Dynamics 365 for finance and operations the default decimal point is set up till 2 decimal place. To change the decimal point according to customers wish follow the following steps. Steps: 1. In the development environment run the Visual studio in administration mode. 2. In AOT find the EDT of the field and change the No of Decimals Property to 4-6 depending on the customers requirement. 3. Compile and build the solution. 4. The changes will be visible on Dynamics 365 finance and operations.

Introduction: There is no limit to what D365 PSA can do. However, it has undergone some significant upgrades. since PSA v3 is a major shift from its previous version, some processes have changed which has greatly enriched the experience of using D365 PSA V3. Let’s quickly look at how you can assign resources and then book them on the Project in PSA v3 using a perfect example. Project I have a sample Project called Grand Chocolatiers Inc. whose schedule looks like this (the WBS is now Schedule in PSA v3) – I will now Assign and Book a Resource to show you how this is done in PSA v3. Assigning Resources: Now, you don’t have any resources Assigned to the Project you just created, so let’s go to the Schedule in the Project and add a new Resource, say, Alicia Baker. I’ve added Alicia Baker without booking her. Coming to the Team and refreshing the grid, I’ll see Alicia being assigned the 12 Hours. Booking Resource: Now, I’ll come to the Resource Reconciliation section and see how I can book Alicia on the task. I’ll select the Previous Difference in order for me to see the distribution I want to book Alicia on. After I double click on the Hours denoted (1), I’ll see an expanded view (2). Now, if I only select the below highlighted days, I’ll be booking Alicia for those hours on the 3 selected days only. Then, I’ll click on Extend Booking. Once I confirm the 3 days that I see, the resource will be booked for that time. And I’ll see the updated Reconciliation View after I book the resource. Now, if you check the Team or the Schedule Board, you’ll be able to see that Alicia is now Booked for the selected duration. Conclusion: Microsoft Dynamics 365 for Project Service Automation enables companies to deliver projects more productively and profitably with higher client satisfaction and this is my personal experience. Today, being a project-based organization, we deliver end to end projects on time and this has helped us achieve an enhanced reputation as a service company. To check out more on the core functionalities and features, please see Kuldeep’s blog below: https://community.dynamics.com/365/projectserviceautomation/b/kuldeepsblog/archive/2018/10/16/reconciliation-view-amp-scheduling-a-resource-in-psa-v3

Introduction: Ever thought of how tracking in Dynamics 365 App for Outlook could be easier? Guess What? Using “Category Based Tracking” you can now easily track Mails, Appointments and Tasks by simply setting a category on them in Outlook. This feature is beneficial as you can select multiple emails, set the category, and the rest is all done for you. We can also provide the same permissions to a delegate and forget about tracking emails, which will be done by them on our behalf. In this article we will go through how to enable Category based Tracking in Outlook and assigning a delegate to do it for us. Pre – Requisites: Outlook D365 Customer Engagement Dynamics 365 App for Outlook Implementation: Step 1: First we must enable tracking using Categories in Dynamics 365. To do this we must import the “Organization Settings Editor” latest managed solution .zip file present at “https://github.com/seanmcne/OrgDbOrgSettings/releases” in our instance. Once done, open the solution and find “TrackCategorizedItems”. As shown below the default value set is “false” and the current value is not set. Click on Add > then an Edit button is shown where we change the value from “false” to “true” as shown, after which everyone in the organization will be able to see the category in their outlook. Step 2: On Opening Outlook after few minutes, in the categories we can see the “Tracked in Dynamics 365”. Step 3: Now if you want to track any particular mail to Dynamics 365, you can set the category of the mail to “Tracked To Dynamics 365”. When the server-side synchronization takes place, an activity record in created in CRM. In a similar way, we can Right Click on Appointments and Tasks in Outlook to track then in CRM. Step 4: To view  tracking progress you can configure the Dynamics 365 App for Outlook which shows the status as Tracking Pending/ Not Tracked/Tracked. Step 5: In addition to this, we can also configure Delegate access so that you provide permission to another person who will performs these tasks on your behalf and track emails. Right click on the Inbox folder in Outlook > Permissions Click on “New” and add the person whom you want to provide the access and click Add. Modify Permission as Required. Note: If you want the delegate to set the “Tracked To Dynamics 365” category you will have to provide “Edit All” permission. Step 6:  Once this is done, the user with whom the mailbox is shared must add the mailbox in their outlook: Right Click on Root Folder > Add Shared Folder > Add email of the user who has shared their mailbox. After which the Shared Mailbox will be visible. To enable the delegate to set categories of the shared folder you must click on “Share” on the top ribbon in you calendar and provide “Delegate Only” Access to the Delegate. The delegate will receive an email to accept and add the calendar, after which he/she will be able to set the categories on the shared folder mails. Note: After the owner of the folder shares the calendar make sure that the permissions that were previously assigned to the delegate are still intact else the categories sections will be disabled for the delegate. Step 7:  To share the details of other folders under the root folder in Outlook, the process is the same, but you will to provide “Full Read Access” permission to the root folder and the desired custom permissions for the required folder. Conclusion: By setting this tracking category to mails on Outlook you can minimize the number of clicks and easily track activities in Dynamics CRM.

Introduction: All these years, I was calculating ‘Actuals’ as the billable hours on the project with the chargeable role. It was a myth that I continued to believe until I stumbled upon the solution that potentially demystifies this myth in PSA itself. Description: Below is how PSA helped to resolve this complex situation and this is how I cleared my understanding towards Actuals vs Estimated in PSA. In the project, I observed that the project was estimated to be a short project of 22 hours and the ‘Actuals’ were of 24 hours. Thereafter, I decided to dig deeper into it to understand the issue of these 2 additional hours, as this was not a big project and getting the additional 2 hours mistake would be very easy. To fix this, below are the actions that I followed: I accessed the Actuals from Project–> Project Name–> Actuals, as shown in the screen shot below. In the grid there, I sorted the “cost” aspect and calculated the number of hours which turned out to be 24. This was strange for me. Then I looked at the “Resource Role” column in the grid and found a 2-hour entry under the Non-Billable role. I pondered why these 2 hours Non-Billable hours are getting summed up in the actuals. But, if thought correctly, even the Non-Billable hours spent by the Resource is an Actual cost to the company. Conclusion: In this way, I could clear the air of confusion surrounding this and for my project budget calculations, I got another field created in the form named billable hours and calculated the sum of all the chargeable roles hours in that field. This now gave me all the three i. e Actuals, Estimated and billed hours in one go. Microsoft Dynamics 365 PSA is the next generation of cloud-based systems which provides an overview of business processes from Sales, Project Management, Customer Service and Fields Service.

D365 For Field Service provides everything you need from optimized work order scheduling to predictive maintenance. While you may have used Microsoft Dynamics 365 for Field service, very few may know about the actual steps required to display Custom Entity in D365 Field Service Mobile App. Let’s see how to display Entity in D365 Field Service Mobile App. 1. Find Entity by using Quick Find feature in Woodford. 2. Select Entity and Click Enable Button. 3. Enable Fields on Entity. Open Fields Section Select Fields to be exposed Click Save button 4. Create Form for Entity. Open Form Section on Entity. Click New Button for Form. Enter Name for Form and click OK. Select fields for display by clicking “Add Field” menu. Design form as per need by dragging fields from Fields Section and click Save & Close button. 5. Create View for Entity. Click View Section. Click New Button. Enter Name for View and Click Ok button. Design View as per need by dragging fields from Fields Explorer Section and click Save & Close button. 6. Display Entity in Home. Open Home tab. Drag Entity from Available Items Section to Home Section. Click Save button. 7. Publish the Solution. Conclusion: Hope the above description explains clearly about the Entity in D365 Field Service Mobile App. There are endless possibilities to what D365 Field service Mobile App can do and displaying entity is just one of them. D365 Field Service is one of the greatest applications that is capable of improving business capabilities and increase efficiency to the highest level.

Introduction: In recent deployments of Dynamics 365 Project Service Automation (PSA) V2 for customers, I’ve come to rely on the chargeability view as a way to modify a quotation and reach the appropriate pricing for a project. In V3, PSA has abandoned the chargeability view. But no need to worry, I will show you how to accomplish the same thing with customer pricing in PSA V3! Steps: Let’s take the example of a quotation I have prepared for the Rotary Club. They need CRM to be implemented. By default, the price list that gets tagged comes from the opportunity that we create or the one that we tag with the quotation. Let’s check the price of a developer in the default price list in the screenshot below. Here, the default price that it shows is $1,250. I built a quotation to the customer based on my default sales price list. Below is what it looks like. The quote now is $12,500 ($1250 x 10 quantity) for 10 hours of requirement gathering. After submitting the quotation to the customer, they came back with a request to reduce the pricing. Now how do we achieve this in V3 which lacks the chargeability view of V2? In V3 we will need to follow these steps: 1. Open the quote 2. Click on “Project Price Lists” as shown in the below image: 3. Click on Create Custom Pricing and PSA creates a custom price list for the quote where you can store the negotiated price like you used to do in chargeability view. 4. Open the price list by clicking on it. There you can navigate to role prices. Select the line on which you want to update the price and click on the edit button that comes up in the header of the grid. Then you can proceed to update the prices based on what you have negotiated. To post the updated prices, click on the activate button. The sequence is shown in the image below. Overall, the process tends to be pretty intuitive. 5. Navigate back the Quote line and follow one more final step: If you open the Quote line details to see if the prices have been updated, you will see that the prices are still the same as the old entries. In order to reflect the new updated roll prices, open the line, go to remove the roll, and re-enter the roll to fetch the updated price. The updated quote with the updated price looks like this: And with that, you have achieved the functionality. Conclusion: Microsoft Dynamics 365 for Project Service Automation enables companies to deliver projects more productively and profitably with higher client satisfaction. Even though PSA V3 has eliminated the chargeability view, it is still possible to access the view in a much simpler way.

Introduction: At times, you are asked to assign certain CRM records to other users and you just have to do it as a part of the process. But let’s face it, you still wonder what might have happened to the record after you assigned it to them but your security roles won’t let you access those. There’s a general D365 setting for this too! You can share your D365 records with other but still retain rights to yourself so keep track of what happened with those later on System Settings: Navigate to Settings > Administration > System Settings In General tab, look for the Setting where it reads as ‘Set whether reassigned records are shared with the original owner’ (quite self-explanatory) Assign Record and check Share Rights: Now, assigning a records from Priyesh to John as shown below – Priyesh would still have rights to the record. Check the Share status of the same. The record will be owner by John but will be shared with Priyesh too. Hope this is helpful!

Have you been added as a Delegate for a fellow colleague but not able to Read, Create or Submit Time Entries on their behalf? Let us see what you are missing. Scenario: William Contoso wants to make Veronica Quek as his Delegate and let her enter time on his behalf. Let’s say William added Resource Veronica Quek as the Delegate above. Error for the Delegate Resource: Now, Veronica is attempting to do time entries for William by going to Time Entry Calendar view and switching the user to William. And when Veronica wants to enter time as William, she’d switch to the User on the Time Entries Calendar View like this – But, see this error and she don’t know what the issue might be. Even though she’s the Delegate! Missing Security Role: Yes, this is the first thing you should check. Veronica Quek is missing a Delegate Security Role in PSA to be able to make time entries on behalf of other users. Assign Delegate security role to the user to make them enter time on behalf of others. And thus, your Delegated User should be good to make time entries.

Introduction: In this blog article, we will see how we can create Item Requirement on insertion of Item Forecast using code. Steps: Create Extension Class for ForecastSales Table that is Item Forecast and using CoC for post insert() method we will initialize Item Requirement. We will call a new class which is created in Step 2. public void insert() {     next insert();     SalesType salesType = SalesType::ItemReq;     CFSCreateItemReqFrmItemForecast createItemReq = new CFSCreateItemReqFrmItemForecast();     createItemReq.initParameters(this);     createItemReq.copyToSalesLine(SalesType); } Create a new class that will initialize values and insert record in Item Requirement form. class CFSCreateItemReqFrmItemForecast { ForecastSales forecastSales; }  In the new class create a method initParameter. This method will initialize ForecastSales object. void initParameters(ForecastSales _forecastSales) { forecastSales = _forecastSales; }  Create another method ‘copytoSalesLine’. It will validate the record and call other methods to copy values to SalesLine Table. public void copyToSalesLine(SalesType _salesType) { ProjTable projTable = ProjTable::find(forecastSales.ProjId); if (_salesType == SalesType::ItemReq) { if (!ProjStatusType::construct(projTable).validateWriteItemRequirement()) { throw error(“@SYS18447”); } } else { if (!ProjStatusType::construct(projTable).validateWriteSalesLine()) { throw error(“@SYS18447”); } } SalesLine salesLine = this.initializeSalesLine(_salesType, forecastSales, projTable); salesLine.createLine(false, // Validation false, // Init from SalesTable true, // Init from InventTable true, // Calc invent Qty false, // Search markup – copied from salesQuotationline false, // Search price – copied from salesQuotationline false, // Check reservation true); // Skip creditlimit check this.updateSalesLine(salesLine, forecastSales); salesLine.update(); } Create a new method ‘initializeSalesLine’. It is called from copyToSalesLine(). protected SalesLine initializeSalesLine(SalesType _salesType, ForecastSales _forecastSales, ProjTable _projTable) { SalesLine salesLine; salesLine.SalesType = _salesType; salesLine.initValue(); salesLine.setInventDimId(_forecastSales.InventDimId); salesLine.ItemId = _forecastSales.ItemId; salesLine.SalesQty = _forecastSales.SalesQty; salesLine.SalesUnit = _forecastSales.SalesUnitId; salesLine.ProjId = _forecastSales.ProjId; salesLine.ActivityNumber = _forecastSales.ActivityNumber; salesLine.CurrencyCode = _forecastSales.Currency; salesLine.initFromProjTable(_projTable, false); return salesLine; } Create a new method updateSalesLine(). It is called from copyToSalesLine() method. protected void updateSalesLine(SalesLine _salesLine, ForecastSales _forecastSales) {     _salesLine.DefaultDimension =       _salesLine.copyDimension(_forecastSales.DefaultDimension);     _salesLine.ProjLinePropertyId = _forecastSales.ProjLinePropertyId;     _salesLine.TaxGroup = _forecastSales.TaxGroupId;     _salesLine.TaxItemGroup = _forecastSales.TaxItemGroupId;     _salesLine.ProjCategoryId = _forecastSales.ProjCategoryId;     _salesLine.CostPrice = _forecastSales.CostPrice;     _salesLine.SalesPrice = _forecastSales.SalesPrice;     _salesLine.LinePercent = _forecastSales.DiscPercent;     _salesLine.LineDisc = _forecastSales.DiscAmount;     _salesLine.LineAmount = 0;     _salesLine.LineAmount = _salesLine.calcLineAmount();     SalesLineType_ItemReq::setSalesLineReceiptDate(_salesLine); }

Introduction: In this blog article, we will see how we can post the journal by using code. How to do? Create a new method and write below code. In this code you declare object of Class ‘LedgerJournalCheckPost’. This class will use journal buffer and post it. public void postJournal(LedgerJournalTable ledgerJournalTable) { LedgerJournalCheckPost jourPost; jourPost = LedgerJournalCheckPost::newLedgerJournalTable(ledgerJournalTable, NoYes::Yes); jourPost.runOperation(); }