Download Swagger file | Note: follow instructions here to setup your own local and self-hosted liteweight RCSU for using the TRY function for each API
#msdyn365fo
D365 Commerce Swagger 9.50.24201.4 [10.0.40]
Download Swagger file | Note: follow instructions here to setup your own local and self-hosted liteweight RCSU for using the TRY function for each API
D365 Commerce Swagger V9.49.24090.3 [10.0.39]
Download Swagger file | Note: follow instructions here to setup your own local and self-hosted liteweight RCSU for using the TRY function for each API
D365 Commerce Swagger V9.46 [10.0.36]
Download Swagger file | Note: follow instructions here to setup your own local and self-hosted liteweight RCSU for using the TRY function for each API
D365 Commerce Swagger V9.42
Download Swagger file | Note: follow instructions here to setup your own local and self-hosted liteweight RCSU for using the TRY function for each API
How to save your D365 F&O customer some money
In most projects, customers and partners are deploying Build and DEV boxes from LCS\Cloud hosted environments. These utilise multiple Azure resources such as storage accounts, virtual network and virtual machines. In many cases, the LCS environment is working against only 1 Azure subscription which is eventually used to host the PROD environment as well. If this is the case, you can potentially save your customer quite some money. In this blog post, we’ll see how much and how!
D365 Retail APIs Part III: How to use the Retail APIs from Power Automate (Flow) and Logic App
After walking through the overall D365 Retail API Architecture in part I and II of this series on the D365 Retail APIs, it’s now time to enable anyone to actually use the Retail APIs. To allow this, this blog post will contain all details on how to construct a request to most of the 400 out-of-box D365 Retail APIs – Beyond that, I’ve included a step-by-step instruction on how to use any of the Retail APIs from Microsoft Power Automate (Flow).
But before we can really get things rolling, we first need to apply some additional D365 setup and we need to choose the right security pattern. So that’s where I’ll start this blog post.
Note: to effectively consume the content of this blog post, please ensure to familiarise with the content of Part I and Part II.