Introduction: A very handy approach for admins and users of Dynamics 365 who want to bulk clean up field values – And just selecting them in Bulk Editing them as shown below doesn’t help!! So here’s the scenario – You want to clear the selected records for their Credit Score field. Because primarily, you can commonly put a value in a field using Bulk Edit, but not clear the value. Workaround: What you can do instead, create a quick and simple workflow to clear the field. 1. Create an On-Demand workflow on Contact entity with an Update step for Contact 2. In the Update step, point to the field and then select the Operator on the right hand side to select Clear. 3. Make sure the Clear appears on the field you want to Bulk Update. 4. Once done, save and Activate the workflow. Run on the selected records you want to clear at once. 5. The values will not be cleared for these records. Hope this helps!

Introduction: This blog explains how we can add files from D365 Portal directly into SharePoint which was long awaited feature missing from Portals. Below are the Steps: Step 1: Set up SharePoint integration from Portal Admin Center 1. Go to the Dynamics 365 Administration Center page and select the Applications tab. 2. Select the name of the portal for which you want enable SharePoint integration, and then select Manage. 3. Click on Set up SharePoint integration –> Enable SharePoint integration. 4. Click on Enable button it will then ask you to sign in again. 5. Enter D365 CE (MS CRM) credentials to sign in again. 6. Click on Accept to grant the required permissions. 7. You will get the below message. Step 2: Enable document management for entities (Customization in D365 CE) NOTE: If document management is not enabled already then follow below steps. Go to Settings –> Document Management –> Document Management Settings Select entity Click on Next and Finish. Step 3: Configure the appropriate form to display documents We need to add Document Location subgrid in the form which will get displayed in portal. (NOTE: Add subgrid on Edit form to edit the record in portal only.) Step 4: Creating and Assigning Entity Permissions. 1. Create entity Permission of Scope “Global” for Case (Incident) Entity. 2. Click on “+” to Add Child Entity Permission for “Document Location”. 3. Click on “New”. 4. Enter below details. Entity Name: Document Location Scope: Parent Parent Entity Permission: Case_Global(Select the name of parent entity from lookup) Parent Relationship: Select the name from drop down. Select all the Privileges. 5. Save the record. 6. Your Global Entity Permission should look like below. 7. After Creating Entity Permission successfully assign web role to the entity permissions. Sign in to Portal 1. Open any Case record. 2. You can see Document Section below from where you can “Add files” or Create “New folder” 3. Click on “Add files” button you are shown a pop-up window from where you can choose the files to upload. 4. You can see the New Folder is created in SharePoint for that Particular Case and file is also uploaded inside respective folder. 5. Click on “New Folder” to create new folder this will get created inside the parent folder “Case_CaseGUID” in SharePoint. 6. From portal you can go inside the folder and then upload files which gets uploaded inside the respective folder in SharePoint. “Add Files” in newly created folder. New Folder and Files in SharePoint.

Introduction: This blog explains the steps on how to enable OnDemand Workflow in D365 CE UCI Apps. Scenario: After clients are upgraded to D365 CE V9 version, Users are unable to use Classic App functionality to run OnDemand Workflows which was showstopper since it was routine task and much needed functionality. Steps: Below are steps to be performed for enabling functionality 1. Admin user should enable the “Microsoft flow” option for all the users. Below are the steps: Navigate to the ‘users’ in Office 365. Post navigation, open a specific user. Enable license for “Flow for Dynamics 365” in D365 CE Plan. (below screenshot for reference). 2.  Enable setting to Show Microsoft Flow in Sitemap. Navigate to Settings → Administrator →System Settings by System Administrator Role User. Open Customization Tab and Enable Microsoft Flow option. 3. Navigate to any Entity below screenshot for Account. Open Account Entity record. Navigate to Flow button on Ribbon and expand options, you will view all OnDemand Workflow for Entity under Run Workflow header. Conclusion: This is how enabling Microsoft Flows setting on specific environment allows Users to run OnDemand Workflows in UCI Apps of D365 CE. Hope the above process helps!

Introduction: In this blog we will see how we can create folder structure in SharePoint for Leads when the record is created in CRM using MS Flows Pre Requisites: SharePoint Integration must be enabled for the required entities Implementation Step 1: Here in our Flows we have used “Create of a record(Leads)” as trigger condition. Step 2: Then we create the folder structure in SharePoint using the “Create File” action Here we will create a text file which can be deleted later if not required. Folder Path: /Lead/Topic_toUpper(replace(triggerBody()?[‘leadid’],’-‘,”)) Here “Topic” is Dynamics value and for the record ID copy paste the expression written above in the Expressions tab and add it at the end of the Folder Path. After we have created the folder structure if the file is not required we can delete the text file by adding the delete step as shown below Step 3: We will also store the Folder ID in a variable “FolderId” to use in the later steps Step 4: Now we will create the same folder structure in CRM (Document Location) Here for the parent site or Location we have we have added the GUID of the Parent Document Location site for Leads. We can get this from the URL of the Parent Document Location record from Advanced Find (Document Location Entity) Lead document location record URL: https://org.crm8.dynamics.com/main.aspx?etc=9508&extraqs=%3f_gridType%3d9508%26etc%3d9508%26id%3d%257b1957C431-5F15-E911-A96F-000D3AF29269%257d%26rskey%3d%257bF5B008AC-07D9-4554-8509-2C05767BFF51%257d&histKey=17520860&newWindow=true&pagetype=entityrecord&rskey=%7bF5B008AC-07D9-4554-8509-2C05767BFF51%7d#371473802 Step 5:  Similarly we can also create sub folders within the main folder as per the requirements Hope this Helped!

Introduction: In this article we will read on how to hide a table or column in Power BI Web Service. Scenario: I have a Power BI Report with 3 Tables; Orders, People and Returns. I want to hide People table when I am publishing the Power BI Report on Power BI Web Service. Steps: Open Power BI desktop file. Right click on the table or column you want to hide Select Hide. Voila! You are done. The Table People we not be visible in the Fields section of Power BI Desktop file. You can find the table in the Modelling view as a Grey table.

Introduction: A field group in table or table extension objects defines the fields to display in a drop-down control on pages that use the table and fields that display when these pages are shown in the tile view. Syntax of fieldgroup is as follows: fieldgroup(<Name>;<Field>) <Name> : It can be either Dropdown, so as to define the set of fields to be included in drop down view or it can be Brick to define the set of fields to be included in a tile view. <Field> : Here, all the fields to be included are specified each separated from the other one by comma. Pre-Requisite: Microsoft Dynamics 365 Business Central Solution: In Business Central, when using the table extension objects one or more fields can be added to the fieldgroup using the ‘fieldgroups’ control. It can be done by using the addlast keyword.Its syntax is as follows: addlast(<Name>;<Field>). In the example below, I created a table extension object in which I have added a new field. I have added that field in the fieldgroup using the syntax mentioned above. Conclusion: Thus, using the above syntax the fieldgroup control can be added to the table in Business Central and even the existing fieldgroup can be modified to add new fields.

Introduction: Difference in configuration of Role Center between Microsoft Dynamics NAV and Microsoft Dynamics 365 Business Central. Pre-requisites: Microsoft Dynamics NAV Microsoft Dynamics Business Central Solution: In Microsoft Dynamics NAV After creation of Role Center. When assigning the Role Center Page to the User the following process is followed. 1. Creating a new Profile in NAV for the and assign the Role Center Page ID . 2. Assigning the User Profile in User Personalization. In Microsoft Dynamics Business Central: 1. Creating a new Profile in Business Central for the required Role Center and assign the Role Center Page ID. 2. Selecting the User Profile directly in the Settings. Conclusion: This is the difference when configuring Role Center Page in NAV and Business Central

Often, when a real-time workflow is being executed in the background, users don’t know how long it will take for the processing to finish. setFormNotifications in D365 v9 come handy! Scenario Here’s how I put my scenario – I call the Real-Time workflow using JS, example, on change of a certain field or the JS being called from the Ribbon button. The JS will trigger the Real-Time workflow I have. Now, while the Real-time workflow is running, the user doesn’t know it has been called and should the user retry the same action? Here’s when the form notification is vital. While the processing is happening, the message will remain as a notification on the form. Once the processing is complete, the notification will be cleared. JS Implementation: For the JS code implementation, the function to call the workflow needs ProcessJS which is available on https://github.com/PaulNieuwelaar/ So on the Form, I’ll add my file after ProcessJS file. Here’s the Account Form code I wrote. I created a JS file to call the Real-Time workflow. In the above code, the Xrm.Page.ui.setFormNotification(Message, Type of notification, Unique Identifier); This will set the notification. Page.ui.clearFormNotification(UniqueIdentifier); will clear the notification from screen. Using this, When the Process enters in Processing mode, the message is shown on screen as “Please wait while processing”. And once the execution is finished successfully, the notification is cleared. Similarly, you can even use this approach for WebAPI calls and have clearFormNotification set in the Success/Failure callbacks. Hope this helps!

Anyone who uses a CRM on a regular basis hopes that it will work seamlessly without errors. But from time to time, when creating and qualifying a lead, confusing error messages popup and leave users wondering about a resolution.  A very common error in Dynamics 365 Project Service Automation comes up when trying to qualify a lead using the Project Information form when the lead is type is set as “Work Based.” The popup below shows the error message: This error cropped up after I did the following steps: Step 1: Create a lead with the basic required details Step 2: Ensure the form selected is Project Information form Step 3: The Type of lead field should have the value Work Based Step 4: Save the lead Step 5: Try Qualifying the lead. This will lead to the above error shown in the screen shot. The best way to resolve this issue is to check the parameter settings, shown in the screenshot below. Upon researching the issue, I found that there is an important parameter setting that is missing, which needs to be changed in order to get to a resolution. When the lead is created, even though we do not have a customer specific price list, PSA asks for a default price list, inferring that this could be a potential customer. The go to place where PSA checks the global parameter setting is Project Service–> Parameters. Click on the default organization unit. In my case, CloudFronts Mumbai. Click on the price list tab (shown in the screen shot below) and then click on the add new project parameter Price List button on the grid. A pop-up opens that asks for the price list. Select the price list and save. Now, when you create your lead in the Work Based type and qualify it, the error will not reappear. With these changes, the price list for the organization unit is updated in PSA. Whenever we use the organization unit again for a quote, contract, or project, this price list will be the default setting. Most importantly, the parameter helps to qualify the lead successfully. This process reflects my personal findings, based on my experience using PSA for the last five years. We have benefited a lot from the implementation of PSA, because we save time and money due to easy access to resources and the ability to manage them.

I was trying to explore the Extend Booking functionality in Dynamics 365 Project Service Automation (PSA) and saw that the users were getting allocated for the entire 24 hours in a day. Immediately, I realized that the issue was coming up because the work hour template was not set properly. When the new work hour template was created, the work hour parameters for the resources were not set back to eight hours. To check the work hours of a resource, navigate to Project Service–>Resources–>Select a Resource. Click on the button “show work hours” as highlighted in the screenshot below. A popup opens. The screenshot shows that the work hours are not defined for the resource as of now. As a result, the resource will be allocated for 24 hours if they are selected for a project unless there working hours are defined.    I selected the resource in the Default Work Hour Template and then created the work hours for that resource (eight hours a day and Monday-Friday working). I assigned these work hours to all the resources in the navigation shown below. Select all resources and click on the ‘Set calendar’ button from the Ribbon Control. I assumed that the new work hours will be set for all the resources selected. I then tried to allocate via extend booking and saw that the resource was still not reflecting the new work hours set. Upon further research I worked out a solution that follows the proper way to define the work hour template of the resources. I created a new work hours template by navigating to Project Service Work Hour Templates. This new work hour template was created to define the following: Working hours per day of the resource. Working days in a week. Holidays in a year. The resource selected should have the proper work hours defined. Select all the resources and assign the newly created work hour template. Because Kuldeep Gupta is a template resource in this example, all the resources will get assigned from Kuldeep Gupta. As a result, it’s not possible to select more than one resource. Now while creating the project select this newly created Work Hour Template  and the project will respect the new work hours. A word of caution: You will not be able to change the work hour template for the old projects as the field is locked and you are not allowed to change it in the midst of the project. I hope that these steps help you to create and assign the work hour template effectively.