In this article, we will learn to use the REST Client in VS Code to test Business Central APIs. We will start by understanding what REST API is. Then, we will install and set up the REST Client extension in VS Code. We will retrieve an access token and use it in HTTP requests to consume API endpoints.
Today I would like to talk about an interesting question I saw last week, how to debug in phone/tablet client session.
Debugging is the process of finding and correcting errors. With Visual Studio Code and the AL Language extension, you get an integrated debugger to help you inspect your code and verify that your application can run as expected.
In the previous blog posts I’ve described the usage scenarios around OAuth client credentials flow for Business Central and how to set it up. The next step is to test the APIs and with OAuth authentication to see if it works properly. In this post, I want to focus on the REST Client extension for VS Code and PowerShell. In the next posts, I will also cover Postman, Insomnia and C#.
When the Modern Client was released with Dynamics 365 Business Central Release Wave 2, Microsoft promised to have fixed a lot of the problems that previously held end-user customers from using the Web-Client:
So, during my last Application course at Readynes in Sweden, we decided that we would run half the course in the Dynamics 365 Business Central Spring Release’s Windows client and the other half in the Dynamics 365 Business Central Release Wave 2’s Modern client
Yesterday we stuck with an issue for a customer which we recently upgraded to Business Central 13.x on-prem. It took time to find the solution so I thought to share a solution with everyone.
Issue Description – Report using custom Barcode Font does not work with Web client but works with the windows client.