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.
With new Dynamics 2018, there is a lot of improvement in a Web Client. One of the first improvements is availability of Print Preview for non-Internet Explorer browsers (Google Chrome, Microsoft Edge, Mozilla Firefox, Safari). In these cases, the Preview button didn’t appear on the request pages of reports. Now it exists.
Generally, when we set up Microsoft Dynamics NAV, the authentication method by default is ‘Windows’.
Windows Authentication : This method allows you to connect to NAV as the current Windows user.
Username Authentication : This method requires that the user provide a User name, Password, and Domain name. Users are authenticated using their Windows account