In this blog we will see the steps in order to send a automated message via Teams as soon as an Opportunity is created in Microsoft Dynamics 365. Step 1: Go to portal.azure.com and select the Azure Logic App Resource. Step 2: Enter all the details such as the Name, Resource Group, Subscription, Region, etc. required while creating a Logic App. Step 3: Select the Dynamics 365 trigger When a record is updated. Step 4: Select Opportunities entity after setting by the Dynamics 365 CRM connection Step 5: Set the data refresh time as required. Step 6: Select the IF action in the next step and the condition would be status_label=won for true. Step 7: Inside True Block select Post a message in a chat or channel option. You can also handle the condition for False block, but in this case we can leave it blank. Step 8: You can post this message in a Group, Channel or send it as a Personal chat. Step 10: Wait for the trigger successful notification. Step 11: Go to Dynamics 365 CRM and navigate to opportunities entity. Step 12: Open a test opportunity or create one if doesn’t exist and close the opportunity as won. Step 13: As soon as you closed this opportunity you may have received the following message. Hence in this blog we saw how we can send messages on MS Teams using Azure Logic Apps on triggering certain conditions. Hope this helped!

Hello,Consider a scenario where we need to have a table (entity) which is a replica of other table or you need some fields replicated into another table. This tool will save a lot of precious time. Let’s say I have a table called ‘Scoping’ and I want fields from that data replicated into another table called ‘ScopingClone’. Steps you’ll take to do this in a time-efficient manner. Step 1: Create a new Table/Entity. (In my case, I created ScopingClone) Step 2: Navigate to XrmToolBox and install ‘Clone Field Definitions‘, connect to your environment and open the tool. As you can see, the fields that I selected are successfully cloned. I hope you found this blog useful.

In this blog we will see how we can open a PDF document on click of button from a record in CRM Let say we have User Guide button on Lead Entity and on click of User Guide button, a PDF document which is User Guide document should be open in next tab. Solution Create a solution and add lead entity only. Then open the same solution in XRM Toolbox – Ribbon Workbench var openUserGuide = { //openUserGuide.userGuide userGuide: function () { “use strict”; Xrm.Navigation.openUrl(“https://sinerleak.sharepoint.com/:b:/s/SingerLewak/EaQO2OWjWA1BnHFCCENV-6EBDkILbg3EfPSFLEu-KCeraw?e=ofVyVB”); } } 4. Add action to command and Publish the solution from XRM Toolbox Output –

Introduction: While using Business Central Web Services or APIs, we often use POSTMAN for testing the request and the responses. Today we’ll see how we can automate this testing to a certain extent using the inbuilt features of POSTMAN. We can have testing logic that runs before every request, after every request or logic that tests on particular request. In the below demonstration, we’ll write automated test to check for GET, PUT, POST and DELETE operations for a single record on a custom API. Postman itself provides a bunch of standard procedures or boiler plate code which we can modify as per our requirements. As this uses Javascript we can also use additional JS features here. Pre-requisites: Postman Business Central OnCloud or OnPremise References: Writing tests | Postman Learning Center Announcing Postman for the Web, Now in Open Beta | Postman Blog Configuration: Post Request – So first we are going to be creating a record in the Customer Table with the following fields. One of the common things to be testing with Custom APIs is to verify whether the request is being created successfully (1) and what we are sending and what is being stored in the record are the same(2). As we are using Javascript, the response is stored in the jsonData variable and we can access any of the fields of the response as a property on the jsonData variable.  As the rest of our automated tests are doing to be performed on this same record, we need to store the Identifier for this record inside some variable which exists outside the scope of this request, here we are using a variable with the Collection scope. If you want to use the same variable outside of this collection, you can also define Global variables.  GET Request – In a simple GET request, the only thing we are concerned with here, is whether the request is executed successfully or not. For this we are simply going to be checking the Status Code. PUT Request – In a PUT request, we are going to be modifying the record that we previously created, here I’m going to update the name of the record. A common test-case for PUT requests would be to ensure that (a) the request is completed successfully and (b) what is being sent in the request is what is updated on the record and is available in the response. DELETE Request – In a simple DELETE request, the only thing we are concerned with is whether the requested is executed successfully and here we will be simply checking the Status Code returned. Once all the Automated Tests are written, you can either execute them from the Collection Level or from a folder level. Here we will be executing our tests from the folder level.  We can also define the Run Order for the requests.  Once the Tests have run, we can get a summary of the results as well as detailed version of the results.  Conclusion: Thus we saw how to use Automated Testing in POSTMAN to reduce re-work and increase efficiency while testing. A bonus tip – you can now use POSTMAN Web Version to create requests instead of download the POSTMAN app and the entire blog above was written using the Web App of POSTMAN. Do note that not everything that can be done on the Windows App can be done on the Web App. Happy Coding!

In this blog, we’ll see how to apply language translation on custom entities, model driven apps and business process flows in Dynamics CRM Step 1- Go to Settings -> Administration->Languages. In Language settings select the required language and click on apply. Step 2- Include all the required components into the solution For example- Custom Entities Model Driven App- For example – Sales Hub Business Process Flow (BPF)- Include the BPF entity as well as process Step 3- Select the solution and click on Export Translation to export the translations to an archived file. Step 4- Extract the contents of the downloaded CrmTranslations_<solutionname>_1_0.zip. This will extract two files. Step 5- After extracting the file, open the CrmTranslations.xml file in excel. You will find 3 sheets in it. Open Localized Labels file, you will find columns for each of the languages you have deployed. Fill in the translations for each language options available. Step 6- Zip the file again and re-import the translations to the same solution using the Import translations button. Step 7- After successful import, click on publish all customizations. Step 8- Go to settings ->Personalization Settings -> Languages. Select the language you wanted to translate into. Output- Hope this helps!!

In this blog we’ll see how to integrate SharePoint with Dynamics 365. Step 1- Configure SharePoint Option in Dynamics 365 Document Management option. Go to Advanced settings -> Document Management. Step 2- In Document Management select “Enable Server-based SharePoint Integration” Step 3- Now in the pop-up screen provide SharePoint site location as “Online” then proceed to next. Step 4- Now provide a valid SharePoint URL and click on finish. Step 5- Enable Share point Document setting for Entities using Document Management Settings. Step 6- Now in the Pop-up screen select the entities that you want to use to manage SharePoint documents. You will find some entities like Account are already Enabled and if you want you can enable other entities. We can also add custom entities if required. Step 7- Check Based on entity, document libraries and folders that are based on Account entity are automatically created on SharePoint site. Step 8- We can store a document for an Account or for any other entity in SharePoint. Open an Account and click on Related tab to choose Document option. Hope this helps!!

Hi Everyone, Isn’t it annoying that you have a text field in your Canvas App which holds a huge information to fit in a small space?There’s a quick solution which you can use to show a mini pop-up by an out-of-the-box feature. Let’s consider an example of where we have a paragraph in a text field then we have output is to be displayed with a limited height and width on the screen. Fig 1: This is a TextInput control where we have a detailed information.Fig 2: This is a normal label/text field control which has limited height and width. (Especially in scenarios like gallery records)Fig 3: This is a ComboBox control with DisplayMode set to View and the DefaultSelectedItems property is set as [TextInput.Text]We can see that when having more data, we can click more and see the entire information. Hope this quick tip helped you in your scenario.

Introduction: Intercompany Transaction is useful feature to track all transaction that is happening with the specific intercompany. Many organizations consist of more than one company, and these companies often engage in various intercompany transactions. It’s important for an organization to be able to track these transactions with ease, and Microsoft Dynamics 365 Business Central allows you to do just that. With Dynamics 365 Business Central, your organization can reduce errors, improve productivity, and post transactions across multiple subsidiary companies. Business Central makes it easy for your organization’s companies to engage with one another in the same way they would with external customers and vendors. Steps to achieve the goal: Intercompany setup Globally search intercompany setup Set the name and check the Boolean “Auto send Transactions” the option to auto send transactions to the intercompany partner as soon as it arrives in the intercompany outbox, and not have to manually send/receive the intercompany transaction. 3. Go to setting icon there is option to Company information. 4. Fill in the Intercompany Partner Code, Intercompany Inbox Type. and Intercompany Inbox Details fields. Conclusion: Thus we saw how we can configure Intercompany Setup and create IC customers and Vendors. Thank you very much for reading my work. Hope you enjoyed the article!

Introduction: Administrators may need to restart a specific Business Central environment to resume normal operation in some cases as a troubleshooting step. Steps to achieve the goal: Go to your settings and select Admin Center. 4. Then click on Restart Environment Action.

Introduction: There might be a need where user wants to cancel the Posted Purchase Credit Memo which was posted by mistakenly. Ideally we cannot cancel the Posted Purchase Credit Memo if it is generated from Posted Credit Memo or Purchase return Order. But if the Posted Purchase Credit Memo is generated from cancel Posted Purchase Invoice . Steps to achieve the goal: If a Posted Purchase Invoice is cancelled then system post the Purchase Credit Memo and cancelled field is set to true in Posted Purchase Invoice. Go to its corresponding Posted Purchase Credit Memo you would be able to cancel action in the Posted Purchase Credit Memo. Cancel action Visibility code added by Microsoft. Conclusion: Thus we saw how we can cancel Posted Purchase Credit Memo in Business central. Thank you very much for reading my work. Hope you enjoyed the article!