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!

In this blog, we will see how we can show activities on Notes in D365 CRM.  Step 1 – Click on Entity and check marked Activities. Save and publish the Entity. Step 2 – Open Main form where you have added timeline, Double click on timeline notes and mark filter by as Show all. Save and Publish the form. Output before enabling the activities Output after enabling the activities

Introduction: Business Central provides us with Change Log which helps us in keeping track of the changes made to a particular field in a particular table. References: Auditing changes – Business Central | Microsoft Docs Configuration: Search for Change Log in Business Central.  Select the tables you want to enable the change log for.  You can set the change log for a particular set of fields or for all the fields in the table.Click on the three dots next to the “Some Fields” and select  the fields you want to audit. Set Change Log Activated to true.  Conclusion: Thus we saw how we can configure Change Log for auditing and tracking changes in Business Central.

Hello, everyone! We know that Recommendations are created using Business Rules, but that only works on Model Driven Apps. As a result, we’ll develop Custom Recommendations that are flexible and customizable to our needs and enhance our App. This is how the Custom Recommendation looks, Let’s start with a simple use case, I want to set ‘Preferred Method of Contact’ field as Phone when User enters data within ‘Phone’ field within the App. Step 1: Add an Edit Form in Canvas Power Apps where the Recommendation would be applied. Step 2: Within Form properties, Click on Edit Fields Add Custom DataCard. Drag your Card below the DataCard where you need Recommendations. Step 3: Within the Custom DataCard, enter necessary information that you like in your App and use below condition. Step 4: For Apply button, I’m using context variables that sets true when click and remains until record is saved or the current screen is Active. Step 5: For changing values in my combo box on field ‘Preferred method of contact’.Note: Based on your requirement, this will change… That’s all. Hope this helps you.

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. 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. Using Shared shift all the transactions done across the store would be captured under one shift.