Recently, I got a question about the little dialogue boxes that sometimes pop up while Microsoft Dynamics 365 Business Central is working. In this video, I should how you can use dialogues in your own code.
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#.
Today we will talk about how to restrict Send to.., Print and Preview button on a standard report.
Is it possible to restrict Send to.., Print and Preview from a standard report in Business Central? You should know that the Send to.., Print and Preview button can’t be hidden. So what we need to do is to report the error after the user clicks Send to.., Print and Preview.
We will subscribe function to restrict standard report buttons.
In this video, I take a look at Field Transfers, the functionality that ensures that field values are moving correctly from master data via journals/drafts to posted data. Several different approaches are used to ensure that and those are explored in the video as well as what to do if you want to transfer your own fields through the system.
OAuth2 authentication method, this type of connection can be used to connect to Business Central Admin APIs; the system to access the exposed APIs services uses a token issued by the access procedure, it is possible to use different ways to get the token released.