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: This blog explains how to Setup POP3/SMTP email configuration in Dynamics CRM. Steps to be followed: Step 1:  Create new Email Server profile. a. Go to Settings –> Email Configuration –> Email Server Profile. b. Click on +New –> POP3/SMTP server. c. Fill Details in the form. Name: Gmail Incoming Server Location: pop.gmail.com Outgoing Server Location: smtp.gmail.com Now Go in Advanced Tab and Provide this Port values for Incoming and Outgoing Port. Incoming Port: 995  Outgoing Port: 587 d. Save. Step 2: Go to Email Configuration settings and then change Server Profile. Step 3:   a. Go to Mailboxes. b. Select the user for whom you want to activate. c. Add following details. Email Address: Enter your Gmail’s Email Address. In Credentials Allow to use Credentials for Email Processing and Provide your Gmail User Name and Password. d. Click on Approve Email e. Click on Test & Enable Mailbox. You may get following error. REASON: Due to hidden settings within Gmail that may be blocking connections from third party apps. SOLUTION:  a. Make sure you access these links while logged into the Gmail account, and make sure they’re turned on/enabled. https://www.google.com/settings/security/lesssecureapps https://accounts.google.com/DisplayUnlockCaptcha b. After enabling again go to mailbox and Click on Approve Email and Test & Enable Mailbox. c. Incoming and Outgoing Email Status is Success.

Introduction: In this blog we will be demonstrating how to call an unbound action using Xrm.WebApi which provides properties and methods to use Web API to create and manage records and execute Web API actions and functions in Customer Engagement The available methods are createRecord, deleteRecord, retrieveRecord, retrieveMultipleRecords,execute and executeMultiple.The execute method executes a single action, function or CRUD operation. Implementation: The syntax for execute method is as follows: Xrm.WebApi.online.execute(request).then(successCallback,errorCallback); Note: This method isn’t supported for Unified Interface and it is only for online mode hence we have to use Xrm.WebApi.online object to execute the method, else it will fail. Step 1: First we create an unbound action. Here in our example we have created an action with the name “new_ActionTest” and we have activated it. In the action steps we have written a step to create a new contact with the name “Jessy David”. Here in our action we an Integer parameter. Any steps can be added as required. Step 2: Below shown code is function used to call the unbound action. Here “boundParameter” parameter is an optional String parameter, we have specified it as null as our action is not bound to any entity. “operationName” is an optional String parameter which is the name of the action.“operationType” is an optional Number parameter which indicates the type of operation we are executing is an Action hence we have specified 0. We can specific 1 for Functions and 2 for CRUD operations. When we run this, the action is called and a new contact is created according to the steps mentioned.

Introduction: In this blog article, we shall see how to pin the power BI reports to Workspace. How to pin? Power BI reports can be added to any workspace that contains a Links section. Once the Power BI reports have been deployed successfully you can pin them to your Dynamics 365 Finance and Operations Workspace. Steps: Open a workspace in Dynamics 365 For Finance and Operations In the workspace, click the Options tab Click Open Report Catelog The list of reports comes from the reports that you have in your Power BI account Click on Ok and those reports will be on your workspace Similarly any customized or out of the box reports can be pinned to your workspace.

Introduction: Create and edit public or system views by using the app designer Description: Dynamics 365 sales app designer allow us to create/edit system view using the app designer. In this example we will use the sales app and account entity for view design. Design: Go to Setting > select My Apps. And open the sales app in app designer. We can define the filter criteria with and/or condition. Select the account view and click on the create new view from the components tab. Adding Column: Now you will able to see the designer page of a view. You can add the column to the view from the components tab I have added the account number column. You need to drag and drop. After adding few columns.   Adding Filter: We can add the filter criteria which will show only related record. We can define the filter criteria with and/or condition   Save the view: Provide the view name and save it   Column Sorting: You can define the primary and secondary sorting column Publish: Finally, you need to publish the view as shown Conclusion: So, this is another quick way you can create Views than just traditionally creating from within Solutions in D365.

Dynamic 365 for field service is an end-to-end solution to manage inventory, manage service orders, track assets as well as handling complex service agreements. It also boots your business by quickly identifying and dispatching resources in turn gaining the intelligence that is required to provide support to the business. Dynamic 365 field service management software helps your business to automate and improve scheduling in order to get the most out of your resources and by dispatching the right technicians. The software proactively detects, troubleshoots and resolves issues to enhance your service experience. This software is able to provide a dedicated self-service portal to its customers with proactive updates and tracking of technicians so that customers get positive impact on their business at every step Introduction: This blog provides a solution to requirement of Client for Call Management in D365 Field Service. Scenario: Most clients specify an requirement where Customers gives a Phone Call to Call Center or send email to Customer Care department and how to design this requirement in Field Service. Resolution: We need to provide solution to requirement as detailed below 1. Create a record of Case from Service Module by Customer Care Representative User as shown below 2. Client has first level of Support team who provide phone support and provide resolution to Customer, then can continue using OOB BPF to Resolve the Case. 3. Other Scenario is Client First Level Support Team is not able to resolve the issue and needs to create an Work Order for Case then User needs to below steps. Set Incident Type on Case and save record, otherwise this will restrict User from Creating Work Order by OOB Validation as shown below. Click button on ribbon with “Convert to Work Order” this creates an Work Order populating all data from Case to Work Order. Note: By Creating Case record below are advantages: First level Support team can review KB articles to resolve the Case. Origin type of record is saved like Phone Call , Email , Web etc. OOB feature to convert Case to Work Order. Conclusion: This blog explains how Phone Calls and email from Customer can be recorded in system and on need basis we can create Work Order from Case record by using OOB feature.

For today’s modern day business that needs customer satisfaction, scalability and digital intelligence, dynamics 365 finance and operations is a complete ERP solution and is one of the most trusted software in the world without any doubt. This ERP solution helps you to innovate your products and processes so that client’s expectations can be met on time and your business can survive well in the cut-throat competition. It also gives visibility to your business across customer sales and service, marketing system and connected distribution. It simplifies production floor management, speeds up product introduction and offers flexibility in delivery alternatives. When it comes to the impact on your finance, you can gain immediate financial insights, drive corporate strategy and growth and through efficient collection management, decrease debts considerably. Introduction: In this blog article, we will see how we can fetch hierarchical data using X++. How to fetch? We will take a scenario where we will pass a category hierarchy and will fetch all categories of that hierarchy and its child category. public class ProductCategoryHierarchy {     EcoResCategory    category;      public void ParentCategory()     {                while select category where category.CategoryHierarchy == “Brands”         {             //code             this.getChildrenCategory(category.RecId);         }       }     /// <summary>     /// get categories of child product     /// </summary>     public void getChildrenCategory(EcoResCategoryId ParentCategory)     {         while select category where category.ParentCategory == ParentCategory         {             //code   this.getChildrenCategory(category.RecId);         }       }  }

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!

Starting from sales until delivery, Microsoft Dynamics 365 offers successful deployment of various business processes. The partners of Microsoft Dynamics 365 list the apps in the app source developed for a specific business need or for a particular business vertical hence showing their expertise. The dynamics 365 application development team has experts who are specialized in developing sophisticated business apps for their partners. The entire lifecycle of the business is supported through Microsoft Dynamics 365 right from developing the apps to listing them in the AppSource and giving support which lets you focus on the core business strategies instead of things which are less important. The qualified team of experts understand your requirements initially and then further work on improving each and every aspect of your business Introduction: This blog explains how to Filter records in PowerApps based on the current user of Dynamics CRM. Steps to be followed: Step 1: Add user entity. For that go to View –> Data sources –> Select Dynamics 365 connection. Select user entity –> click on connect. Step 2:  Now select Browse Screen and add Label control on Browse screen. Set its visible property to false. Set Text property to: LookUp(Users,internalemailaddress=User().Email,systemuserid) Step 3:  Select Browse Gallery and set its Items Property to : Search(Filter(Cases,_ownerid_value = Label1.Text), TextSearchBox1.Text, “description”) (Here Label1 is the name of Label which we have added in previous step && _ownerid_value stores the owner of that particular case record) I have selected _ownerid_values because owner field stores the user value according to which we want to filter the case records. By following above steps you will be able to filter records based on current user.

Introduction: In the blog we will be discussing about the error while connecting to Dynamics 365 version 9 using console app. Implementation: In our example we will show how to connect to Dynamics 365 using a Console app in v 8.2 and when the same code is used to connect to version 9 we get an error. We will also discuss about how to resolve the issue Step 1:  The code show below is used to connect to Dynamics 365 version 8.2 using Console App. Step 2: When we run the above code, we get the following output. Step 3: Now we change the credentials and try connecting to Dynamics 365 v 9 with the same code, we get the following error. Step 4: To solve this issue there are two ways, in the first method, set the Target framework to “.NET Framework 4.6.2 or above”. Step 5: After changing the target version build the solution again and run the app.The connection to Dynamics 365 version 9 environment will be successful. Step 6: The second method is by using the below code before making a connection. TLS stands for “Transport Layer Security,” and is a protocol that is an industry standard designed to protect the privacy of information communicated over the Internet.