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: In this you can create the tasks for yourself and assign tasks to others or be assigned a task by someone else in your Company and you can set an expiration date, create a recurring task. User Task Functionality: Reminds the work to be done You can assign tasks to yourself or others Set start date / due dates if needed. You can Link the List pages or Reports. We can make recurrence for monthly, weekly, quarterly, or annual tasks. Set priority (High, Medium, Low) You can view and manage the assigned tasks from Role Center Create User Tasks: In global search, search for User tasks. Click on ‘New’ button for adding a task. When you click on the new button it opens up a card page to enter the details about the task. Enter a Subject, Task Description, Due Date, Start Date, and Priority. enter a ‘User Assigned to’ and optionally use the ‘Link Task to:’ of Page or Report and Set the Report or Page the task should be linked to. We can also create a recurring task by clicking on ‘Recurrence’ action. Enter the ‘Recurring Start Date’, a formula for the repeating the task and the number of occurrences and click ‘OK’. When you gave the occurrences as 12 it will create a new 12 tasks from the recurring start date. After Click ok, the tasks now show on the ‘Pending User Tasks page’ sorted by Due Date. Conclusion: We can also edit and modify the task, such as changing the user the task is assigned to, the % Complete, the Priority or the Due Date.

Introduction The September 2018 Update of Power BI has finally brought to users, the functionality to copy data from a table or matrix in a report. This has been a much-requested feature as one often finds themselves needing to copy a value or columns of data from a report with no option to do so. Steps: Now, if you want to copy a value, several columns  in a table or matrix you can do so by following the steps below: Copying one value :  Select the value->right-click on the selection -> select ‘Copy Value’ -> An unformatted value will now be added to your clipboard. Copying several columns of data: Select all the data in the required columns->right click on the selection and select ‘Copy Selection’.-> The required data and column headers are copied to the clipboard. In a Matrix, when you select one value->right-click-> ‘Copy Selection’-> All measures required are copied along with the value ( as shown in the screenshot below). Conclusion: This is a long-awaited feature of Power BI and will definitely enhance user experience while navigating and using Power BI reports.

Problem: There is no in-built function in SSRS where we can count the number of Saturdays and Sundays between any two dates in SSRS. This is a needed function for scenarios where we only need to get a count of working days.’ Solution: Following is a formula that can be used for getting an accurate count of weekends. = (((DateDiff (DateInterval.Day, DateAdd(DateInterval.Day,7-WeekDay(Parameters!startDate.Value),Parameters!startDate.Value), DateAdd(DateInterval.Day,7-WeekDay(Parameters!endDate.Value),Parameters!endDate.Value).AddDays(1)) + 1)/ 7)*2) + iif(weekday(Parameters!endDate.Value)=7,1,0) + iif(weekday(Parameters!startDate.Value)=1,1,0) -1 Here instead of Parameters!startDate.Value and Parameters!endDate.Value, you can use any other Start Date or End Date.

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

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. Note: Before using shared shift make sure that all the existing shifts at all the POS terminals of the store are closed. Steps: Login with user id at the main MPOS terminal. Open a new shift Now login at all the other terminals of the store Select the option: Resume an Existing Shift Perform Sales and other functions on all the devices End of the day before closingthe shifts Make sure that all the users have logged off from the other terminals except Main MPOS. On the Main POS: Close the shift. Conclusion: Using Shared shift all the transactions done across the store would be captured under one shift. At one particular time only one shift can be shared.