POS and headquarters extensions
|Enabled for||Public preview||General availability|
|Admins, makers, or analysts, automatically||Aug 2, 2019||Oct 1, 2019|
Many retailers need or choose to extend Dynamics 365 Retail to modify the existing business logic or add some new feature to the product to meet their business goals. In the point of sale (POS), commerce runtime (CRT), and headquarters (HQ), we are adding more extension points to support custom business scenarios. The goal of this feature is to add the necessary core extension points in the product to support extension scenarios.
After moving toward the binary-based extension model, we are wrapping and exposing all our core POS logic and user interface (UI) controls as SDK (APIs) to help the extension to easily consume and override our logic. Without these APIs, it will be difficult for the extension to write some custom logic. In some cases, the extension has to rewrite some of the existing code or write too many lines of code to do a simple scenario. To avoid this and to reduce the number of lines of code, we’re introducing more advanced APIs and configuration-driven development to simplify the overall development process.
POS UI and API extension
We are continuously enhancing the POS framework to add more POS APIs to consume our logic in extension and UI extension points to add custom columns, app bar buttons, and custom controls in core POS views.
POS overridable requests and triggers
New overridable requests are added in POS to override the POS workflow or POS business logic and to add custom logic or validation. POS trigger framework helps you to run custom logic before or after core POS logic. With this new pattern, developers can easily customize any workflow in POS.
Retail POS APIs (docs)