msdyn365fo

Why I am a fan of a Single Company setup for Retailers in D365 F&O

Implementing D365 F&O requires some specific Design considerations when it comes to Retail organizations. A Retail company is not simply organized by Legal entities which transact with each other and 3rd parties. A Retailer has one or more brands to protect. Consumers expect the same brand experience anywhere anytime. This experience cannot have interference from legal entity boundaries or the way an ERP system is configured.

Too often, I see D365 F&O Solution Architects and Consultants automatically translate a Retailer’s subsidiaries to companies in D365 F&O. Even if this does not align with the way the Retailer is organized (central backoffices) and/or their logistics model is setup (hub and spoke). But first and foremost, it can shatter Order fulfillment into pieces and significantly raise operational complexity and overhead with detrimental impact on the Customer Journey..

IS THERE AN ALTERNATIVE FOR THIS?

Read the full story here in my Linkedin article

Patrick Mouwen | september 29, 2023 | AX - Functional| d365commerce, intercompany, legalentity, msdyn365fo, Retail, singlecompany |

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.. 😉.

Patrick Mouwen | februari 28, 2022 | D365 - Technical| API, api management, APIM, apimanagement, azure, azure api management, bestpractice, cloud scale unit, cloudscaleunit, CRT, d365, d365 commerce, d365 f&o, d365commerce, d365retail, developerportal, Dyn365FO, flow, integrations, Interface, interfacing, logic apps, logicapp, msdyn365fo, ODATA, retailserver, scaleunit |

How to unlock many hidden D365 Commerce Features

How to Unlock Many Hidden D365 Retail Features!

Ever since D365 Finance & Operations V10, we’re in the Managed Updates model which aligns all Customers on a similar Platform Version – It’s the so called “One Version” strategy which brings a lot of benefits. But is there really ONE VERSION in reality? We have License keys, Parameter modules, SysFlighting and Feature Management which already contains 250+ Features in V10.0.11 PEAP. Did you all enable them? If you sum all these parameters, D365 Finops installations can fundamentally differ even if the underlying Platform version is similar.

Now with D365 Retail (Commerce) there is yet another variable – A relatively new Retail/Commerce Parameter area which is controlling Retail functionality behind the scenes… In this blog post we’ll dig out all the Features that can be enabled from here. Fellow Functional and Technical D365 Retail/Commerce consultants sit tight: this area is likely to become more and important in the future. It can also be really helpful for your own customisations.

Patrick Mouwen | mei 11, 2020 | AX - Functional, AX - Technical - INT| Commerce, Configuration parameters, CRT, d365, d365 commerce, d365retail, Dyn365FO, Features, Flighting, msdyn365fo, Parameter, Retail, Retail parameters, Unlock |