In this blog, I am going to showcase how to resolve the issue in purchase orders at the time of receiving. Once the purchase order is confirmed and try to receive it, you may run into the below error. This issue is happing because purchase order lines are not updated properly. When you are received the purchase order line using excel add-in, the purchase order line will not be imported properly. Use data entity in data management to import purchase order line.  Steps to resolve this issue in the purchase order. Open the purchase order. Select the purchase order line for which you are facing this issue. In the line details, Check the inventory quantity. The quantity must be there, you will face this issue because the inventory quantity is blank. If the Inventory quantity is blank, then click on the Purchase order tab and make a change request. Click on edit and update the inventory quantity, according to purchase order line quantity, and Save the purchase order. Confirm and again try to receive the Purchase order. In the receive tab, click on the product receipt. If you are facing this issue for multiple purchase order lines then cancel that Purchase order. Create a new PO and import the purchase order line with the data entity. Hope this helps!

In this blog, I am going to showcase how to resolve the issue in Payment Method on Retail POS. When a customer will come to the shop and want to buy an items with a different payment methods like check, currency then getting the above error on the POS. This error occurred because, in the payment, Some configuration was missing. Steps to identify the missing configuration in the Payment method. Go to all stores and select the store for which you are facing this issue. Click on Payment method. Select the payment method for which you are facing this issue. In the General tab, the operation name must be there. In the Posting tab, all the account number must be setup. Save and Go to Channel Database and run full sync for 1070, 1090, and 1110 jobs. This will take 15-20 minutes to save the data. Refresh the POS link and this issue will resolve. hope this helps!

In this blog we will see how to integrate Microsoft Teams with Dynamics 365 Solution Step 1- To enable Microsoft Teams in D365, Go to Settings –> Administration –> System Settings –> General Tab and flip the below highlighted options to Yes. Step 2- Once done, we’ll be able to see Collaborate button on the ribbon Step 3- Open a record and click on Collaborate Step 4- On Collaborate with Microsoft Teams window, you will see one of the following: If there’s no channel: You can connect the current record or view to any team channel by selecting, Get started. If there is channel that’s already connected: Select a channel from the list and then select, Start collaboration. This will open Microsoft Teams and navigate to the channel that you selected. Or, connect the current record or view to a new team channel by selecting, Create a new connection. Then click on start collaboration. Step 5- Add Dynamics 365 from + button

Introduction: Business Central provides us with Web Services which we can use for CRUD operations on specific tables. However it also provides us with different methods of accessing specific records for CRUD operations. Pre-requisites: Business Central On-Premise or OnCloud. References: https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/properties/devenv-odatakeyfields-property Usage: In Business Central, if we do not specify the ODataKeyFields as a property on the Page that we’ll be using as Web Service, then by default we have to use the Primary Key. However if we specify the “ODataKeyFields” in the page, we can use the field we have specified as the key for pulling the record in Web Services. While there are no limitations on which field can be used as key field, keep in mind that Business Central fetches the first record matching that field. For instance if you use the “Buy-from Vendor No.” as the ODataKeyField, then the Web Service will fetch the first matching record sorted by the Primary Key. Standard Business Central APIs use the “SystemId” field as the ODataKey field. You can also use multiple Keys in ODataKeyFields and use them for fetching records. Conclusion: Thus, we saw how we can use ODataKeyFields property for fetching records and performing CRUD operations. As a side note, you can also use multiple keys in ODataKeyFields.

MS Forms offers a functionality to create a dropdown field which is similar to an option set fields in D365 CRM, But when it comes to mapping or storing values between these two field things become a bit tricky. However there are a few workaround using power automate capabilities. In this blog let’s see how we can store a MS Forms Dropdowns options into an Option Set field in CRM.  What is an Option Set? Option sets are a field type that can be created within Dynamics CRM and are Often referred to as “dropdown” or a “pick-list”.   An option set has two identities for each of its option. The Options Label Name and the Label Value as shown in the below snapshot.  What is a Dropdown in MS Form ? A dropdown is a list of defined options(Choice) that can be selected by a user, unlike a text field where the data can be “organic” or manually entered.  Now Let’s Consider an use case :  Consider we have a MS Form Name “Company Registrations” when a user submits this form a Power Automate flow is triggered which creates a new Account record in CRM with the field mapping shown in similar colors in the below snapshot.   Now we need to get the form responses first to create a new Account record.  2. All the Text field values can be directly mapped into the dataverse connector as shown in the below snapshot.  3. For mapping the MS forms Dropdown to the Option set we need to maintain the CRMs Option Label values into our flow as to set (define the value of the option set) Option Sets in CRM we need to pass the Label Values to the flow (if you just pass the label text it won’t work hence we need to maintain these option set values in the flow)as shown below.  4. Now we need to select the option set field in our flow connector and select enter custom value.  5. Once you are able to add a customer value use the following expression which will dynamically bring option set label value for the dropdown choice selected by the user on the form.Expression – outputs(‘Option_Set_Values’)?[outputs(‘Get_Form_Response’)?[‘body/rf98dd4fb83624fc7b7314de77542a3ef’]]Red : Text in the above expression corresponds to “Outputs “in the below snapshot which is the output of the compose in which we stored our option set label values. Blue : Text corresponds to the “Ownership Type” from the form response.   Output : MS Form Submission –   Created Account Output –   Hope this helps !  

After PowerAutomate was added in PowerBI as a preview feature, it is finally available for general use. In this blog we are going to use this PowerAutomate visual to export PowerBI data into CSV and upload the CSV on Sharepoint. Open PowerBI Desktop and drag the PowerAutomate Visual, if it isn’t available in the visualization pane update your PowerBI Version. Now add the columns, you need in your CSV file. Click on the ellipsis button on the visual and select edit. Create new flow and select instant cloud flow. A default PowerBI trigger would be created, click on add new step. Search “Compose” action in the search bar and select it as we have to compose PowerBI Raw data first. In the Inputs select PowerBI Data. After composing we have to convert this data into CSV, therefore add “Create a CSV table” step and add previous output. Now we have to upload this CSV into sharepoint so we will add a step to create a sharepoint file. Enter the Sharepoint address, Folder Path, give the file any name desired and put “.CSV” as suffix. Save and close the map. To run the flow, press Ctrl and left click. As you can see the file in SharePoint is created. Thanks for reading, hope this blog helped!

To keep track of all your customer data in one place, you may want to import contacts, leads, or other record types into Dynamics 365 Customer Engagement (on-premises) from other sources, such as from an email program, a spreadsheet, or your phone. In this blog we will be looking on how to import bulk data from excel and populating it in Microsoft Dynamics 365 CRM. Use Case: Importing Bulk amount of Leads into Microsoft Dynamics CRM. Solution: Step 1 : How to download a template for data import Go to Settings > Data Management > Templates for Data Import. Select the entity that you want to import the data for from the drop down list, then click Download. (Note) You can use a text file, a compressed zip file, an Excel spreadsheet, or Excel workbook to do the data import. The template will have the fields of that particular entity as the columns to be filled by the user. Adding all the details for the lead to be imported. Step 2 : How to import leads with a template Go to Settings > Data Management > Imports. Click on Import Data > Browse. Choose the file you’d like to upload, then click Next. In this example, I used Lead.xls. (Note) If you used a template for the lead upload, your data will automatically be mapped. If not, see Above for how to get a template for the upload. 4.) Set the owner on the Review Settings and Import Data screen, then click Submit. Once submitted, your lead will show up on the My Imports leads screen. When the upload is completed, the status will show as “Submitted.” 5.) Open Dynamics CRM to see whether the data has been imported or not as in the excel sheet. You can further use this according to your requirement either to import Accounts, Contacts and for many other Entities related customizations. Hope this helps !

Hi in this blog we will see how we can add rows to power bi dataset for a given date range. For example if you have a dataset which has start and end date and you want rows for each date between this range then this blog will help you. Step 1: Open Power BI load your dataset and go to transform data. Right click on your from date column and change its type to date. Step 2: From add columns click on custom column Step 3: In custom column formula add following code: { Number.From([From])..Number.From([To]) } Step 4: Expand this column to new rows to get your result. Step 5: Change the datatype of this column to date. In this way you can prepare your dataset for all the dates present in your From and To column. Hope this helps.

Introduction: Business Central provides us an easy method of modifying our data from within Excel using Web Services commonly found in the Edit in Excel action. This can be seen in the commonly used List Pages for example Payment Terms. However this functionality can be missing for certain pages or you might want to have additional logic or filtering before executing this. For this I’ll be demonstrating how to add the “Edit in Excel” action in Business Central pages. References: Viewing and Editing in Excel From Business Central – Business Central | Microsoft Docs Using Filter Expressions in OData URIs – Dynamics NAV | Microsoft Docs Configuration: In the above piece of code, I’ve added the “Edit in Excel” action onto the Blanket Sales Order SubForm to allow for easily adding lines using Excel. Firstly, we define the filters that we will be using on the page that we will be passing in the “EditWorksheetInExcel” procedure of the “OdataUtility” codeunit. Note that these filters are defined as Odata expressions as the “Edit in Excel” functionality uses Excel behind the scenes. In the next lines, we see that we pass the Page Caption, the page ID and the filters to be set on the page. Under the hood, the procedure creates a Published Web Service using the provided Page ID and uses that for the data manipulation. We had to prepend the additional “00000” as the procedure has been hardcoded to use “COPYSTR(“00000″ + {PageID}, 5)” meaning it starts reading after the 5th character. Conclusion: Thus we saw how to configure Edit in Excel for pages that do not have built in Excel functionality. Also note that Microsoft is expanding the Excel functionality to List Parts from Business Central v19 Wave 2, you can read more about it here.

On some instances, there are Managed fields in Dynamics 365 CRM (or CE if you want to call it) where we can’t change the required level of the field from Fields i.e. on the database level. And you get the below error – Here’s an alternative way to do it. Scenario Let’s consider this scenario. Although Microsoft suggests you don’t change the behavior of Managed fields since they are designed with a purpose. However, let’s consider this scenario where you want to make the Parent Account for Lead as required on the form.When you try to change the Requirement Level as follows And while saving this change, you get this error. So how do we do it? Let’s see. Workaround – Business Rule Now, to overcome this particular scenario you can implement a simple Business Rule to make it required as follows – If the field can’t be made Required on a database level, you can make it required on the form using Business Rule. Here’s how you create your Business Rule.As the Business Rule starts with the condition, here’s the check you need to add in case the field value is not entered. The condition I used is as below – Check if Parent Account for lead Does Not Contain Data If this is True, then go ahead and add a Step for True condition. Add Set Business Requirement Level And in this, you need to set the Business Required Status to Business Required as show below. And the result is the Business Rule which looks like in #1 above. Now, save your changes, Publish the Rule, Activate and check. The result will be that the field is not required once it doesn’t have data forcing the user to enter data for the same. Hope this is helpful!