DOCSEARCHbyAlgolia
Submit Docs

Dynamics 365 Unified Operations Public Documentation

repository·main·Indexed 18 days ago

https://github.com/microsoftdocs/dynamics-365-unified-operations-public

Documentation for Microsoft Dynamics 365 Commerce, focusing on the mass deployment and servicing of sealed self-service components. It covers CDN implementation options (Commerce-provided Azure Front Door, customer-owned Azure Front Door, and external CDN services) and developer guidance for extending Commerce Data Exchange (CDX) synchronization using XML metadata to automate push and pull operations between headquarters and channels.

Tokens
295.9K
Snippets
293
Records
1.1K
Agent score
62%

What's inside Dynamics 365 Unified Operations Public

  1. Overview of the Finance and Operations development experience

    main

    The development experience for finance and operations apps is designed for cloud-based ERP applications (public, private, or on-premises). Key characteristics include:

    • Decoupled Development: Tools are decoupled from the running environment. Development is performed against local, XML-based files rather than directly against an online database.
    • IDE: Microsoft Visual Studio is the primary development environment, customized specifically for the platform.
    • X++ Compiler: The X++ compiler generates Common Intermediate Language (CIL), which is the same managed intermediate language used by .NET languages like C#.
    • UI Development: Developers leverage a browser-based client and specific design patterns for forms to enhance end-user experience.
    • ALM: The Application Lifecycle Model supports build automation, test automation, and the deployment of models to the cloud.

  2. Overview of modernized payment flows

    main

    The Dynamics 365 Commerce POS is transitioning to a React UI framework to provide more efficient, single-pane payment flows.

    Key Modernized Flows:

    • Pay Card: Provides Swipe card (directs to terminal) and Enter manually (for unreadable chips/stripes) options. It includes a Payment amount screen for subamount entry and visual indicators (symbols) for terminal status and processing.
    • Pay Cash: Features a dedicated pane with direct amount entry and Smart denominations (logical groupings of currency).
    • Pay with Gift Card: Automatically checks and displays the gift card balance before processing redemption.
    • Pay with Loyalty: Allows cashiers to search for customers or view/select associated loyalty cards directly within the payment flow.

  3. Overview of Fiscal Integration for Commerce channels

    main

    Fiscal integration in Dynamics 365 Commerce is a framework used to register sales in compliance with local fiscal laws. It enables integration with fiscal devices (like fiscal printers) or external web services (operated by tax authorities) to prevent tax fraud and ensure transaction inalterability through digital signatures.

    To implement custom or region-specific fiscal logic, developers can either extend an existing fiscal integration sample from the Commerce SDK or create a new sample. A sample typically includes extensions for the Commerce Runtime (CRT), Hardware station, and POS.

  4. Overview of Fiscal Printer Integration for Poland

    main

    This sample provides a way to integrate Microsoft Dynamics 365 Commerce Point of Sale (POS) with a fiscal printer in Poland. It extends the standard fiscal integration functionality and specifically supports the POSNET THERMAL HD 2.02 protocol for fiscal printers from Posnet Polska S.A.

    Key Technical Details

    • Communication: Uses a native software driver to communicate with a fiscal printer connected via a COM port.
    • Implementation: Provided as source code within the Commerce Software Development Kit (SDK).
    • Testing: The sample was tested using a Posnet software emulator for the Posnet Thermal HD FV EJ fiscal printer.

    Note: Microsoft does not provide the hardware or the Posnet software/documentation. You must contact Posnet Polska S.A. for hardware and operational details.

  5. Overview of Dual-write integration

    main

    Dual-write is an integration technology used to synchronize data between finance and operations apps and customer engagement apps (Dataverse). It enables near real-time data synchronization, ensuring consistency across different business applications.

    Key areas of focus for developers and architects include:

    • Core Concepts: Understanding the purpose and benefits of dual-write.
    • Setup: Configuring system requirements, connection settings, and security roles.
    • Management: Customizing mappings, handling multiple table maps, and managing errors after the initial setup.
    • Mapping: Aligning data models between apps (e.g., Customer Master, Vendor Master, Product, and Organization Hierarchy).
    • Troubleshooting: Resolving issues during setup, initial synchronization, or live synchronization.

  6. Overview of Fiscal Registration Service Integration for Austria

    main

    To comply with Austrian local fiscal requirements for cash registers, Dynamics 365 Commerce provides a sample integration between the Point of Sale (POS) and an external fiscal registration service. This sample extends the standard fiscal integration functionality.

    Key Technical Details

    • Base Solution: Based on the Electronic Fiscal Register (EFR) solution from EFSTA.
    • Protocol: Communication with the EFR service is handled via HTTPS.
    • Hosting: The EFR service can be hosted on the Retail Hardware station or a separate machine accessible by the Hardware station.
    • Implementation: The sample is provided as source code via the Commerce Software Development Kit (SDK).

    Note: Microsoft does not provide the EFSTA hardware, software, or documentation. You must contact EFSTA directly to acquire and operate the EFR solution.

  7. Overview of the Sweden control unit integration sample

    main

    This sample provides a reference implementation for integrating Microsoft Dynamics 365 Commerce Point of Sale (POS) with Sweden-specific fiscal devices known as control units.

    Key Capabilities

    • Automatic Registration: Automatically registers sales, returns, and receipt copies in a control unit connected to the Hardware station.
    • Fiscal Response Capture: Captures the control code and manufacturing number (collectively called the fiscal response) from the control unit and saves them to the transaction. This data is viewable on the Store transactions page.
    • Receipt Customization: Allows adding custom fields for the control code and manufacturing number to receipt layouts to print the fiscal response.
    • Reporting: The Electronic journal (Sweden) channel report includes the fiscal response for transactions.
    • Error Handling: Supports several workflows for registration failures:
      • Retry: Attempt registration again if the unit is disconnected or unresponsive.
      • Defer: Postpone fiscal registration.
      • Skip: Mark the transaction as registered while including info codes to capture the reason for failure.
      • Verification: Check control unit availability before opening or finalizing a sales transaction.

    Technical Context

    • Hardware Requirement: The control unit must be physically connected to the Hardware station paired with the POS.
    • API Reference: This sample uses version 1.1.4 of the CleanCash Type A API by Retail Innovation HTT AB.
    • Limitation: The sample does not support customer order scenarios.

  8. Overview of the Store Commerce app

    main

    The Dynamics 365 Commerce Store Commerce app is a Windows Presentation Foundation (WPF) shell application for Windows that unifies Modern point of sale (MPOS) and Cloud point of sale (CPOS/Store Commerce for web). It uses the Microsoft Edge WebView2 control and the Chromium engine to render the user interface, providing better performance than the UWP framework used in MPOS.

    Key capabilities include:

    • Cash-and-carry transactions and shift management
    • Customer engagement, clienteling, and assisted selling
    • Endless aisle and order processing/fulfillment
    • Inventory management and reporting
    • Support for local hardware station and offline usage
    • Direct integration with payment terminals, printers, and cash drawers

  9. Overview of Fiscal Registration Service Integration for the Czech Republic

    main

    To comply with Czech Republic local fiscal requirements for cash registers, Dynamics 365 Commerce provides a sample integration for the Point of Sale (POS) with an external fiscal registration service.

    This sample extends the standard fiscal integration functionality and is based on the EFSTA EFR (Electronic Fiscal Register) solution. It enables communication via HTTPS to ensure Electronic Registration of Sales (EET) by transmitting sales data to tax authority web services.

    Key Details:

    • Service Hosting: The EFR service can be hosted on the Commerce Hardware station or a separate machine accessible by the Hardware station.
    • Implementation: The sample is provided as source code within the Commerce Software Development Kit (SDK).
    • Requirement: The EFR solution itself is not provided by Microsoft; you must obtain it from EFSTA.

  10. Overview of simplified electronic invoicing for Saudi Arabia

    main

    Microsoft Dynamics 365 Commerce supports Phase 2 requirements for electronic invoicing in the Kingdom of Saudi Arabia. This functionality allows for the generation, signing, and submission of simplified e-invoices to the Zakat, Tax and Customs Authority (ZATCA).

    Key capabilities include:

    • XML Generation: Creating an XML file of a simplified e-invoice upon completion of a sales transaction in Commerce POS.
    • Digital Signing: Generating a cryptographic stamp (digital signature) for the e-invoice.
    • QR Code Generation: Printing a QR code on the receipt that includes the cryptographic stamp.
    • ZATCA Submission: Submitting simplified e-invoices from Commerce headquarters to ZATCA for reporting purposes.

  11. Key features of the Dynamics 365 mobile app

    main

    The mobile app provides several capabilities for business process mobility:

    • Offline Capabilities: Users can view, edit, and act on business data with intermittent or no network connectivity. Data is automatically synchronized once a connection is re-established.
    • Business Logic Extensibility: Developers can optimize offline capabilities using the Business logic extensibility framework to ensure rich and fluid mobile scenarios even when offline.
    • Code Reuse: Mobile workspaces use existing Dynamics 365 code assets, meaning validation procedures, business logic, and security configurations do not need to be reimplemented.
    • Workspace Designer: IT admins and developers can design workspaces using a point-and-click workspace designer within the web client.

  12. Available integration patterns for finance and operations apps

    main

    The following integration patterns are available for connecting finance and operations apps with third-party services:

    PatternDescription
    Power Platform integrationIntegration via Microsoft Power Platform.
    ODataOpen Data Protocol for synchronous, real-time data access.
    Batch data APIAsynchronous integration using the Data management package REST API or recurring integrations.
    Custom serviceCustom business logic exposed via SOAP or REST.
    Consume external web servicesConsuming services hosted outside of finance and operations.
    Excel integrationIntegration via Microsoft Office.

    Note for on-premises deployments: The only supported API is the Data management package REST API (available on 7.2, platform update 12 build 7.0.4709.41184 and later).