Microsoft Dynamics 365 for Retail – Extensibility workshop
Transcript of Microsoft Dynamics 365 for Retail – Extensibility workshop
Microsoft Confidential – NDA Required
Benefits undeniable
Benefits undeniable
Customer environment
MicrosoftPartner/ISVs
Simplified servicing model
No code merge
Speed
Simplified customization
model
Easy Maintenance
Latest and greatest version
Microsoft Confidential – NDA Required
POS Extension
What Can I do?
Dev
New POS Operations
New and modify existing views*
Customer and Order Attributes
Enhanced Triggers
POS Controls, Custom controls and Dialogs
Data list and App bar extension
Error and Log framework
Retail proxy and Hardware station APIs
Localization framework
POS Extension
New Extension project template
Extension Manifest
Support for Multiple extension projects
More to come…
POS Framework
Show journal
Product search
Welcome screen and Transaction screen
(Layout designer)
Product and Customer Details
POS Views
Customer Add/Edit
More to come…
App Bar, Header split view, Menus
Toggle switch, Pivot, Spinner, time and Date
POS Controls
More to come…
Attribute driven extension for Customers
POS Configuration driven extensions
More to come…
Microsoft Confidential – NDA Required
AX Extension
Follow the extensibility pattern to extend
any Dynamics 365 for Operation
components.
What’s coming
Dev
Extension models and packages
Code extensions: Events, Plug-ins and Class
Form and Table Extensions
View and Data entity extensions
Menu, Query, Report extensions
Security roles, EDT and Enums
AX Extension
https://ax.help.dynamics.com/en/wiki/customizati
on-overlayering-and-extensions/
Dev
Retail statement class extension
CDX extension
Retail Extensible Enums
Retail Transaction service class extension
More delegates and events
AX Extension
Microsoft Confidential – NDA Required
DB Extension
What Can I do?
Dev
No CRT schema extension
Extension schema
Deployment check
DB Framework
Packaging
Attribute driven extension for Customers and
Orders
Extension at CRT service layer based on entity
PKs
Device and Channel configuration view
More to come…
Configuration parameters
DB Extensions
Microsoft Confidential – NDA Required
Hardware station Extension
What Can I do?
Dev
Override
New
Pre and Post
HWS Extension Pattern
New Request/Response based extension
pattern
Supports pre and post triggers
New Device extension
More to come based on feedback…
New operation extension
HWS Extensions
Microsoft Confidential – NDA Required
POS Extension
What Can I do?
What’s coming
Dev
POS Extensibility packaging des
Microsoft POS project\Extension.json
Build and sign(No code merge, extensions
are seperated)
Custom MPOS self-service package
Modern POS Production
Testing in UAT
ISV Extension Project
\Manifest
Partner 1 Extension project
\Manifest
Partner 2 Extension project
\Manifest
Microsoft Confidential – NDA Required
Engagement model
What Can I do if extension points are
not available for my scenario?
Dev
Engagement model
Publish
Engagewith us
Dynamics 365 for Retail
Analyze + Transform
Microsoft Confidential – NDA Required
Engagement model
Sources for sharing AX customization
details
Dev
Engagement model
Extend/migrate the
customizationOptimize
Analyze and Design Implement Validate & Release
Extension points
Code upgrade
CARRuntime
Customization
package
Tele
metr
y so
urc
es
Sources for sharing AX customization
Customer/ISV
name
Target date for go-
live
Priority Customization scenario/Business
process
Class name:
Method name:
Extension point details:
Sample:
Need to modify the method signature, sql in code, long
method or need to change the while statement in method A or
some logic
Table:
Table methods:
Extension point
details:
Enums: Views:
Maps:
Macros:
Template:
Customer/ISV
name
Target
date for
go-live
Priority Customization
scenario/Business process
POS
Screen shot, code files or
more details about the new
extension point, like need
support for new operation,
need to add column in
show journal screen or new
view etc.
CRT
Service name:
Extension points needed:
Share the details of which
service you are planning to
extend and why (feature gap
etc.)
Extended Channel DB
Proc name:
View name:
Table name:
Share the details of DB artifacts
you are planning to extend and
why (to add new columns etc.)
Extended Hardware station
Device name:
Share the details of what are you
planning to extend and why. (to
ad support for printing multiple
logos etc.)