FastTrack for Dynamics 365 for Operations...What's New in spring release (July 2017) Changes Follow...
27
Transcript of FastTrack for Dynamics 365 for Operations...What's New in spring release (July 2017) Changes Follow...
AGENDA
What’s New in Retail POS Extensibility
Agenda:
➢ New in spring release
➢ POS Extensibility architecture
➢ Overview about POS extension pattern
➢ POS APIs, Controls and View extension
➢ Samples and demo
➢ Channel DB extensibility pattern
➢ Engagement model
What's New in spring release (July 2017)
Changes
Follow the extensibility Patterns
Dynamics 365 for Finance and operation SKU
POS
Channel DB
RS and CRT
Hardware station
Dynamics 365 for Retail SKU - Hard Sealing
HQ
POS
Channel DB
RS and CRT
Hardware station
Dynamics 365
for Retail SKU –
Retail only
(Fully sealed)
Dynamics 365 for Retail SKU –
Retail + Finance
and Operations (Fully sealed)
Dynamics
365 for
Finance and
Operation
(unsealed
X++)
Benefits
No code merge
Speed
Simplified customization
model
Easy Maintenance
Latest and greatest version
Customer environment
MicrosoftPartner/ISVs
Simplified servicing model
POS SDK
POS SDK Nov 2016
POS SDK
POS SDK July 2017
.
Extension List
Extension 1
Request/Response APIs
(Operations, Data access
APIs, workflow)
Retail proxy
Views (Create/Extend)
Override Request/
Response (APIs)
Triggers
Dialogs, controls, Custom
controls
Extension N
Request/Response APIs
(Operations, Data access
APIs, workflow)
Retail proxy
Views (Create/Extend)
Override Request/
Response (APIs)
Triggers
Dialogs, controls, Custom
controls
POS UI SDKPOS API
Cre
ate
/C
on
su
me
Request/Response APIs
(Operations, Data access APIs,
workflow)
Views
Controls and Dialogs
Custom fields and controls
Triggers
Existing viewsLocalization (Resx) and Error
Logging
Templated Dialogs Templated Dialogs
Override Request/Response
(APIs)
Ext
en
d
CSS layouts and themes
Knockout bindings
Consume
PO
S S
DK
Ext
en
sion
Dynamics 365 for Retail POS Extensibility Architecture
Extension Manifest Extension Manifest
Categorizing POS Extensions
• Two categories of extension types:
• Extend existing POS functionality – These extensions modify POS by adding/modifying functionality to/of existing pages or workflows
• Create new functionality – These extensions supplement POS by introducing new pages or workflows that do not exist “out of the box”
Extending New Functionality
Extending POS Pages
➢ Custom App Bar Buttons - Adding custom buttons to the App Bar on select pages
➢ Custom Column Sets – The ability to replace the grid columns with a custom column set on select pages
Extending POS Workflows
➢ Triggers – POS Triggers were ported to the new extensibility model
➢ Override – Override POS workflows
Creating POS Functionality
➢Custom Controls Controls that can be reused on different extension views
➢ Templated Dialogs
Dialogs with custom content that all utilize a common dialog framework
➢New Operations
Add new retail operations that are defined in HQ and executed in POS.
➢New Request Handlers for the POS Runtime
➢Custom Views
Create new pages and navigate to them from other extensions
Consuming POS controls
• Extensions can consume POS functionality by executing requests via the POS runtime
➢ Feature specific requests like Add Item to Cart, Get Product, Get Current Cart, Get Customer, etc.
➢ Functionality based requests like Show Message Dialog, Open Cash Drawer, Print Receipt, etc.
➢Extensions also use POS Runtime to execute retail server requests for custom APIs
➢POS UI SDK - Library that exposes POS controls to extension views enabling extension views to maintain a consistent look and feel
➢Most commonly used controls are available with samples
POS Packaging
Channel DB Extension
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
Customer attributes
HQ:➢ Attributes for Customer
POS➢ Customer/Add edit screen
➢ Customer details
➢ Customer panel in transaction screen
➢ Customer search – Sample extension (Attribute as column and Search by attribute*)
Order attributes (Header & Lines)
HQ:➢ Call center orders
➢ Update channel orders
POS
➢ Customer orders
➢ Cash & Carry
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.
CRTService name:Extension points needed:
Share the details of which service you are planning to extend and why (feature gap etc.)
Extended Channel DBProc 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.)
Extend/migrate the customization
Optimize
Analyze and Design Implement Validate & Release
Extension points
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:
Code upgrade
CAR
Runtime Customization
packageTele
met
ry s
ou
rces
