D365 – Technical
D365 Commerce Swagger 9.51.24298.6 [10.0.41]
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 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
D365 F&O/Commerce interfacing via Azure API Management: My Best Practices
I am seeing more and more customers and partners who actively promote the use of Azure API Management for D365 F&O backend and/or D365 Commerce Scale Unit ODATA interfacing. See for example, this blog post by Adrià Ariste Santacreu. However, there’s still a significant number of customers and partners who shrug their shoulders while thinking: “Why would we use it when we can interface ‘directly’?”. In this blog post I’ll address this question by sharing my best personal best practices in using Azure API Management for D365 F&O backend and/or D365 Commerce Scale Unit ODATA interfacing. But before sharing the best practices, we first have to explode the myth that interfacing via Azure API Management (APIM) would not be DIRECT.. 😉.