In Basic authentication, we used an actual user to connect to BC, but with the new S2S authentication we are not using an actual user and Scheduled tasks must be created and executed in the context of a licensed user. Therefore API requests cannot schedule a background task. It is simple as that.
Category: Azure Integration Services
This is the 3rd blog post of the OAuth series, and I have already completed the numbers 2 and 4. Once I complete this blog post today (Hopefully), I only have one to write. I will try to complete that one also within next week when I find some time during the night. I have …
In my previous blog post, we have gone ahead and registered an application in Azure Active Directory and then create an application account in Business Central. As the last step, we have granted permission from Business Central.
In this blog post, I’m trying to briefly explain what we did in little bit more detailed way.
It is by default when Logic Apps exposes an HTTP Trigger Request, it uses an HTTP POST method. Recently one of my colleague asked is it possible to change the trigger Method to GET. Yes, this is very much possible. When the Logic Apps was initially released it was only able to support the POST …
If you are working on Logic App to integrate Microsoft Dynamics 365 Business Central with any other third party application, by now most probably you must have used HTTP requests or custom connectors (mainly with SOAP web services). I saw a couple questions in the forum asking how to access action output in Logic App. …
Today I did some work with a Logic Apps and one of the requirement was to call a Business Central function through a Web Service. I normally use Postman to simulate requests, export the collection and use that to create the Logic App connector. Codeunit which I published as a web service had few functions …