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.

Introduction: In this blog article, we will see how we can fetch Form Control and its value which is of different datatype in EventHandler in D365 Operations Scenario: I am working on Global Address Book functionality for checking Duplicate values for PartyID (String), Tax Id (CheckBox) and Tax Id Type (ComboBox). I am using Event Handler of form method to enable a button based on value of above three fields. Steps: Create Event Handler with below code: [PostHandlerFor(formStr(DirPartyCheckDuplicate), formMethodStr(DirPartyCheckDuplicate, enableSearch))] public static void DirPartyCheckDuplicate_Post_enableSearch(XppPrePostArgs args) { FormRun formRun = args.getThis() as FormRun; FormCheckBoxControl TaxId = formRun.design(0).controlName(“TaxId”) as FormCheckBoxControl; FormStringControl PartyNumber = formRun.design(0).controlName(“DirPartyTable_PartyNumber”) as FormStringControl; FormComboBoxControl TaxIdType = formRun.design(0).controlName(“TaxIdType”) as FormComboBoxControl; FormControl searchBtn = formRun.design(0).controlName(“searchBtn”); if(TaxId.value() || PartyNumber.valueStr() || TaxIdType.valueStr()) { searchBtn.enabled(true); } else { searchBtn.enabled(false); } }

Introduction: In this blog we will discuss how we can solve XML issue while importing solution from one environment to other. Scenario and Steps: 1. Deploying a solution from one environment to other causing issues below issue. This error occurs when there are some integrations enabled for your entity. 2. Click on “Help me resolve this issue” and a Dialog will be opened which shows the specific error. As you can see element “IsMSTeamsIntegrationEnabled” is present in the solution which is not present in target solution. Thus we will remove this element from XML and import the solution. 3. To remove the element from XML follow the below steps: Extract the solution you want to import. Open customizations.xml file. Remove “isMSTeamsIntegartionEnabled” element from XML and save the XML. Zip all the files and import the solution to your environment. Your solution will be imported to the targeted environment.

Introduction: When facing a task of naming a new file, every personnel will name it accordingly what may think is the best. You can organize and manage documents more effectively. Organizations should have a standard naming convention for documents, libraries, lists and pages in SharePoint Online. To improve the user experience for SharePoint, here are few points to consider while naming a document. General Instructions: 1. No Spaces – Spaces on the Internet are “%20”. It is the character encoding for space. So, do not provide spaces while naming any document library, documents, etc. Instead, you can use underscore “_ “or dash “- “in place of a space. 2. Make sure document versioning is turned on so that you can store, track & restore files in SharePoint Online. 3. A name should be meaningful and make sense. 4. Dates – Dates are commonly used for two objects “Articles” and “Documents”. For article place the date in front of the name like “20180911_Article” For documents dates should be placed at the end of the name like “Document_20180911” Date Format – yyyymmdd. 5. Make it short and simple – The file name should be as short as possible without losing its potential to be identified and searched. Longer names take more time to search or read. SharePoint includes file name as well, so the short name will make short URL. We can use abbreviations – Invoice can be “INV”, Quotes can be “QTE” 6. No special character, except “_” & “- “. 7. Data Order (From general to specific) – We can consider using the abbreviation (Point 5) followed by Project and then date. We can also consider adding versions & document id. Example – INV-CloudFronts-20180911.pdf 8. For Site Pages – It is not a best practice to name pages with a “_” or space. Instead, it is recommended using “-“. Example (This-is-a-site-page). 9. Many organizations like to prefer placing versions numbers in a document name. Place the version at the end of the file name. Use dash “- “to separate major versions and minor versions or drafts. Example (Document_V01-01.docx). Here, V01 is the major version and “-01” is the minor version. 10. Do not change the name of Lists & Libraries. Conclusion: A simple naming convention is a best way to avoid naming related issues or accidental overwrites which affect end users’ experience. Though it varies from company to company, but each organisation should have a standard naming convention.