To edit the mappings of Business card scanner control, refer below steps. Select the Settings icon, and then select Advanced Settings. The Business Management page opens. On the navigation bar, select Settings, and then under Customization, select Customization. Select Customize the System. Under Components in the solution explorer, expand Entities, and then expand the Contact or Lead Select Forms. Open the form of type Quick Create. Locate and select the Business Card field on the form, and select Change Properties in the Edit In the Field Properties dialog box, select AI Builder Business Card control on the Control Select the property that you want to change the mapping for, and select the Edit icon to change the value the field maps to. When done, select OK.

Introduction:   We had a requirement, where using MS flows, we had to set the field named Outreach which was a datetime field as blank. For a  date time field,null expression cannot be directly set and so we could not clear the existing Date in this field When I tried to set null, it failed with an error “Minimum value for date can be 01/01/1753”.   Solution: We used the below work around. Add a step Convert Time Zone, add base time as Null. Since we are not actually converting from any time zone, we can keep source and destination time zone as same. For the record on which we want to set date as null, configure run after as below. For the date, now set converted time instead of null Conclusion: The date will be cleared and set to blank.

Introduction:   When we create a view, We can configure the sort but the sorting is available only for the columns which are a part of the entity on which the view is created. Eg: In the active accounts view, there is a column ” Email” which is a field from Contact Entity. If we see the columns available for sorting we cannot see Email. However, in case you want to sort on a column from the related entity we can do it using the view designer and Fetch Xml builder tools from the XRM Toolbox. Solution: On load of My active accounts, the default sort is on Account Name Open View Designer on XRM Toolbox Click on Edit Query to open Fetch XML Builder We can see the order attribute is on name Now, we can edit and add order attribute to emailaddress1 After you click on Return FetchXML, you will return back to view designer. Then click on edit XML and remove the disable sorting on the attribute. You can now save and Publish.   Conclusion: The View My active accounts will be by default sorted by email address in ascending order.

As an Administrator, you might face this situation and suddenly you are not able to see one of the Channel in Microsoft Teams. There might be a chance that it got deleted somehow. Will you be able to recover the deleted Channel? The answer is Yes as a Team owner you will be able to recover the deleted channel. You can restore any deleted channel up to 21 days. In this article, we are going to see how to restore deleted channels, auditing, and other preventive measures. Restoring a deleted Channel in MS Teams: Go to Microsoft Teams > Click on Team whose Channel got deleted. Click on the 3 dots beside and then go to the Manage Team. Go to Channel option, expand Deleted items. You will see all the deleted Channels listed over there. Click Restore. By default, all the Members of the team have the right to delete the Channel in Microsoft Teams. After this incident, you might want to remove delete permission for the Team members. Please find the steps below. Go to the Team for which you want to manage permissions. Click on the 3 dots beside and then go to the Manage Team (as we did while Restoring the channel). Go to the Settings option, expand “Member Permission”. Uncheck “Allow members to delete and restore channels”. You can manage other permissions as well as per your organization requirements. If any channel got deleted, you might want to know who has deleted this, to ensure it doesn’t happen again. We can search for the Audit logs from Security and Compliance center. Login to Security & Compliance center (protection.office.com). On the left navigation, Go to Search > Audit log search. Select the activities, you want to search for. In this case, we need to find who deleted the Channel. Scroll down to MS Teams activities. Provide the start date and end date and then search. You can leave the Users field blank. Click on Search. You can find the deleted channel activities on the right-hand side. You can also set up Teams retention policy for chat and channel messages and decide whether to retain data, delete it or retain for a specific period.  Find the steps below to setup Retention Policy. Go to Office 365 Security & Compliance Center > Information Governance > Retention > Create. Name your Policy and add a description. You can set the Retention Policy for Retain Data or Delete Data. Retain Data – This will ensure that your data is retained for a specified period. Data is retained and is available for eDiscovery even if the user deletes it. You can define whether to delete data or do nothing after the Retention period is over. Delete Data – If you set up the Retention policy to delete data after the defined time. Choose Microsoft Teams as a location. You need to select if you want to apply Retention policy for Teams Chat and Channel messages. Review your settings and create the policy. In this article, we saw how we can restore a deleted channel, managing members permissions, checking the Audit logs and applying Retention Policy which will help your organization to manage MS Teams more efficiently. Thanks!

Some Retailers may want to encourage customers to pay via cash in their Retail stores. This can be made possible by offering discounts to customers if they pay by a Cash mode of payment. In this way, they can help reduce the expense of credit card processing fees. Therefore, retailers might provide discounts to customers who use these alternative tender types. In Dynamics 365 Commerce (Retail) a new type of discount has been introduced which is called as tender based discount. In tender based discounts, as a Retailer you are able to give different discounts based on the payment medium the customer has chosen to pay. Even though tender-based discounts reduce the subtotal of the transaction, automatic charges that are applied to the transaction aren’t affected. For example, if the delivery charges are calculated as $5 because the subtotal was more than $100, and the tender-based discount reduces the amount so that it’s less than $100, the delivery charges are still $5 for the order. In the system you can go to Retail>Pricing and discounts >Tender discount. Here you can set up the parameter as required, add price groups and then run necessary jobs to apply it in Retail POS. In the below example the payment type selected is Cash. You can select any type of method as per your need.

Introduction: We had requirement where we wanted to send Email using Power Automate. We had already implemented this using Work Flow. While implementing this using Power Automate, we started receiving mentioned issue “You are not authorized to send mail on behalf of the specified sending account.” We had similar issue while implementing the same using Work Flow, But it did not work for the Ms Flow, after doing RND we came to know that we need to give permission to send the mail on behalf of another user.   Solution : Please follow the below steps to give permission to specific user. Step 1: Go to  Admin Center -> Select Exchange Admin Center. Step 2: Click on Recipients and Select User you want to give permission and  follow the steps as shown below. Step 3: In this scenario, We wanted to send Email from Admin on behalf of Support User. Below are the Steps to Give the Permission: i.   Go to mailbox delegation. ii.  Click on the “+” icon and add User from which you want to send Email. In this scenario, we wanted to the send Email by Support. So, add Admin into Send as and Send on behalf and Full Access. ->Save and try to run the flow. Hope this will help you while sending an Email on behalf of the another User.

Introduction Power Automate has finally got one of the most awaited features. Let me explain it to you. So, if you are willing to deploy similar type of actions inside flow, you had no option but to write each action separately from the beginning. phew! That sounds like lot of work! But now, thanks to Power Automate, flexible solutions have emerged to save time and create better user experiences, which means now you are not required to write each action distinctly every time right from the start, instead just copy and paste actions in Power Automate! Voila! There you go! Copy Click on ellipsis (…) on action which you want to copy or duplicate. Click on “Copy to my clipboard” Paste Click on “Add an action” Go to “My Clipboard” Under My Clipboard you can see all the actions which you have copied. Select the action which you want to paste.

Nowadays, Test Automation is the most important requirement for any company to check Quality assurance of their product or software. There are very few tools available for Test Automation of MS Dynamics CRM. In this blog, we are going to see how we can do Test Automation using TypeScript Library (D365-UI-Test). It is the opensource library you can edit as per requirement and if any issue is present in the repo you can create an issue on Github Repo. Florian Krönert will resolve the issue as soon as possible. GitHub Repo Link: https://github.com/digitalFlow/D365-UI-Test Setup and Installation: We will use Visual Studio Code because it is a lightweight Code Editor with integrated Git support. And we will require git to clone directory, and we can do operation directly from the VS Code editor itself.   Installation Process: First, we will be required D365-UI-Test Source Files So, we need to clone that Repo from GitHub remote GitHub Repo to Local Machine in your working project directory. To open Terminal inside the VS Code use the keyboard shortcut Ctrl + `   In terminal run following git command to clone the directory git clone https://github.com/DigitalFlow/D365-UI-Test.git Now after cloning the repo, we need to install the required Node Packages that are required to run the Project.   To Install the required Node Packages, navigate in the project directory in the VS Code and run the following command. npm install “npm install” command will install the required Node Packages with a specific version which will be defined in the “package.json” file. After the installation of all required packages.   Now, we can see the sample test cases written in the “TypeScript” in “spec” Folder. To write your own test cases we need to add our test cases and run the Project. Following is the Folder structure of the D365-UI-TEST Project you will get after setup:   In the above screenshot, you will able to see the “spec” folder, we can add our own Test Cases but there are some sample test cases available for the UCI “xrm-uci-ui-test.spec.ts” which is written in TypeScript.   Now, we must add the settings.txt file in the folder structure so that we can pass the CRM Login Credential to the Test Case File. Or else you can directory pass credential in the Test Case itself.   After Adding the setting file, we need to give the relative or absolute path of the Setting file as follows:     Following is a test case to login to CRM instance and created the Account Record:   To the Run the Open the Integrated Terminal to Visual Studio Code. OR Press Ctrl + ` And Run the following command: npm run test   It will run all the tests and show the result as to which test as passed and failed. If the test is failed, then it will show the error of why the test has failed.   Once the test is run from the terminal it will open the chromium-browser and start the test. You can see the Documentation of the Library in GitHub or in following mentioned link: https://digitalflow.github.io/D365-UI-Test/

Introduction This blog explains how we can trigger Power Automate based on the required condition. Suppose you have a requirement where you want your flow should get trigger based on some condition then you can check condition on “Trigger” itself rather than adding a new action to check condition. Use Case: Trigger flow when Lead is created and Lead Source Type is “Trade Show” Trigger flow when Lead is created and Flag is “Yes”. Trigger Flow when Lead is created, Lead Source Type is “Trade Show” AND Flag is “Yes”. Trigger Flow when Lead is created, Lead Source Type is “Trade Show” OR Flag is “Yes”.   Steps to be followed: Trigger flow when Lead is created and Lead Source Type is “Trade Show” Click on Ellipsis (…) –> Click on Settings Go to Trigger Conditions and Click on “+Add” Add condition. @equals(triggerBody()?[‘leadsourcecode’],7) NOTE: “Lead Source” is an option set field add value of that option to check. After adding condition click on Done. Test your flow.   Trigger flow when Lead is created and Flag is “Yes”. Repeat step number 1 to 3. NOTE: Flag is the “Two Option” field for two option set fields use true or false in condition. @equals(triggerBody()?[‘cf_flag’],true)       Trigger Flow when Lead is created, Lead Source Type is “Trade Show” AND Flag is “Yes”. Repeat step number 1 to 3. AND Condition @and(equals(triggerBody()?[‘cf_flag’],true), equals(triggerBody()?[‘leadsourcecode’],7))   Trigger Flow when Lead is created, Lead Source Type is “Trade Show” OR Flag is “Yes”. Repeat step number 1 to 3. OR Condition @or(equals(triggerBody()?[‘cf_flag’],true), equals(triggerBody()?[‘leadsourcecode’],7))

However, it seems there’s no “e-mail activity” in Azure Data Factory. I would like to send an e-mail notification if one of the activities fail. In this blog I am going to explain you how to send an e-mail notification using ADF Web Activity and Azure Logic App. Sending an Email with Logic Apps Logic Apps allows you to easily create a workflow in the cloud without having to write much code. First login to Azure.portal.com Choose to create a new resource, search Logic App Click on Create button, it will be asked to specify some details for the new Logic App: Click on Review + create again to finalize the creation of your new Logic App. After the app is deployed, you can find it in the resource menu. Click on the app to go the app itself. Click on Logic app designer link. In this tip, we need the HTTP request (“When a HTTP request is received”) as the trigger, since we’re going to use the Web Activity in ADF to start the Logic App. From ADF, we’re going to pass along some parameters in the HTTP request, which we’ll use in the e-mail later on. This can be done by sending JSON along in the body of the request. The following JSON schema is used: { “properties”: { “DataFactoryName”: {             “type”: “string”         }, “EmailTo”: {             “type”: “string”         }, “ErrorMessage”: {             “type”: “string”         }, “PipelineName”: {             “type”: “string”         }, “Subject”: {             “type”: “string”         } }, “type”: “object” } We’re sending the following information: The name of the data factory. Suppose we have a large environment with multiple instances of ADF. We would like to send which ADF has a pipeline with an error. The e-mail address of the receiver. An error messages. The name of the pipeline where there was an issue. The subject of the e-mail. In the editor, click on New step to add a new action to the Logic App: Click on New step it will send the e-mail. When you search for “mail” you will see there are may different actions: Click on Office 365 Outlook and select Send an email(V2) Once you’re logged in, you can configure the action. We’re are going to use dynamic content to populate some of the fields The result look like this: Once you click on Save, it will generate HTTP POST URL. Copy this URL for ADF. Triggering the Logic App from ADF Suppose you already created pipeline with some activities in ADF: Add a web activity to the canvas and connect another activity to this new activity using the arrow. When the connection has been made, right-click on the connection to change it to a Failure precedence constraint. This will change the color of the connector to red. Now we are using HTTP POST URL that will copied from the Azure Logic App We also need to add a header, where we will set the Content-Type to application/json. In the body, we enter the following JSON (following the structure mentioned before): { “DataFactoryName”: “@{pipeline().DataFactory}”, “PipelineName”: “@{pipeline().Pipeline}”, “Subject”: “An error has occurred!”, “ErrorMessage”: “The ADF pipeline has crashed! Please check the logs.”, “EmailTo”: “myemail@outlook.com” } We’re using system parameters to retrieve the name of the data factory and the name of the pipeline. All the other fields in the settings pane can be left as-is. Now we can run the pipeline and wait to see if any emails come in: I hope this will help you.