Release notes for Sitecore Commerce 8.2 powered by Microsoft Dynamics August 2016

Release notes for deploying Sitecore Commerce with Microsoft Dynamics Retail AX 2012 R3 CU10 (internal version name AX6) or Microsoft Dynamics Retail AX (internal version name AX7 CU1). Microsoft has discontinued external versioning as of AX7. This document contains information on late breaking developments, known issues, and workarounds.

  1. What's New

    Added compatibility with Microsoft Dynamics AX7, and continued compatibility with AX6.

    AX7 Federated Authentication.

    AX7 Federated Payment.

    New methods, a repository interface and implementation, and new object types have been added to the Payment service layer. For more information, go to the Sitecore Commerce Connect Developer Guide on http://doc.sitecore.net.

    Federated Payment is now supported in the StarterKit storefront, and a sample Federated Payment service has been included for testing purposes with the Commerce Connect StarterKit on GitHub.

    Federated Payment is now supported in the Reference Storefront for Sitecore Commerce powered by Microsoft Dynamics AX 7 through Sitecore Commerce Connect.

    AuthenticationTokenProvider

    To support authentication by using tokens in all of the Commerce Connect APIs, an AuthenticationTokenProvider has been introduced. It consists of an interface defined in Sitecore.Commerce.Config and a default implementation which always returns NULL, meaning no token is provided.

    The introduction of the provider centralizes the logic of providing the Token. The base class ServiceProviderRequest that is used in all service methods as input parameter has been extended with an AuthenticationToken property. The property can be set explicitly on every call made through Connect. If the property is not set, the AuthenticationTokenProvider is instantiated and called, and the return value is assigned to the property.

    The AuthenticationToken is defined as a class that can be customized for extensibility purposes. For more information, go to the Sitecore Commerce Connect Developer Guide on http://doc.sitecore.net.

    AX7 replaces the Transaction Service.

    Support for Preserve External Settings in Merchandising Manager. There is now support for the Preserve External Settings feature in Merchandising Manager. When integrating with an external commerce system or ERP, Merchandising Manager can be used to edit Catalogs, Products, and Categories fields that are defined in Sitecore, while fields sourced from and managed by the external system remain read-only.

  2. Compatibility
    Microsoft Dynamics AX6 CU10.
    Note: Please update your AX instance before installing Commerce components.
    Microsoft Dynamics AX7 CU1.
    Note: Please update your AX instance before installing Commerce components.

    Sitecore Experience Platform 8.2.

    Sitecore Commerce Connect 8.2.

    Commerce Server 11.4.

    Reference Storefront 8.2 from GitHub.
    Note: Be sure to use the most recent version of the Reference Storefront from GitHub.

    To upgrade from a previous release, review the Breaking Changes section in this document, and install the new versions of all packages.

  3. Resolved Issues

    Some of the issues described in this document contain internal reference numbers listed in parentheses. You can use these reference numbers to communicate with Sitecore about a particular issue or feature.

    • SCpbMD cannot sync more than 1000 products from AX. (22075)
    • AX product image sync fail with duplicated attribute names in different attribute groups. (467680)
  4. Known Issues
  5. Breaking Changes

    The AX6 Routing Framework has been replaced by the Data Exchange providers. It is necessary to manually migrate settings configurations from the Routing Framework to Data Exchange.

Sitecore Commerce 8.1 powered by Microsoft Dynamics

  1. What's New
  2. Compatibility

    Tested with Sitecore XP and Sitecore Commerce Connect 8.1.

    Commerce Server 11.3

    This update is compatible with Sitecore 8.1. Be sure to use the most recent version of the Reference Storefront from GitHub.

    This update is compatible with Microsoft Dynamics AX 2012 R3 CU10. Please update your AX instance before installing this product.

    To upgrade from a previous release, review the Breaking Changes section in this document, and install the new versions of all packages.

  3. Resolved Issues

    Previous Bugs Fixed:

    9391 - Synchronization fails if a product does not belong to at least 1 category in Dynamics

    9378 - Order History: When viewing a new online order in the storefront, an error occurs if the P-0001 Channel Transaction job has been run

    7318 - Registering a new user will sometimes not work, other times take too long

    9293 - When running synchronization console tool for first time you "get item failed" for Request History item

    7359 - Submitting an order takes too long

  4. Known Issues

    A full sync of the Routing network is required if you remove a category association, a product, or a variant.

    No validation done to check promo codes

    When a user adds a promotion code to a shopping cart, no validation is done to ensure that the promo code is valid or applicable.

  5. Breaking Changes

    Transaction Service updated to support multiple Dynamics AX Online Channels

    The Transaction service has been updated to support multiple online channels within a single Transaction Service instance. This aligns with the new Reference Storefront, which supports multiple storefronts in a single Sitecore instance, each referencing a different online channel.

    New Custom Profile Provider

    This release includes a new Custom Profile Provider, which allows personalization of the storefront based on mapped information from a Dynamics AX profile. This includes being able to personalize based on a customer's Loyalty tier or point level. This feature requires the customer to be logged in. This provider provides extensibility to allow further customization to map additional properties from an AX profile to further enhance customization.

    Indexing Improvements

    Calls to Dynamics AX during indexing have been removed, improving performance while indexing.

    Conversion to Property Bag for most Dynamics Attributes

    Dynamics AX properties are no longer directly mapped as full properties in Sitecore Commerce Server. Because Dynamics AX supports different property schemas in each channel, better support for multi-channel means handling mapped properties in a more generic way. Now, by default, Dynamics attributes end up in a new property bag. It is possible, by directly manipulating the schema in the synchronization tool, to "promote" a property to be a first class property, if that becomes necessary.

    Product Relationships Mapping Improvements

    Product relationship mapping has been improved to remove some hard coded mapping and multiple relationship types surface on the storefront easier. Dynamics AX does not push the localized names of relationships through the Publish API, so even if you have created localized relationship names in AX, we are only able to synchronize English names.

    Synchronization Issues

    This release supports incremental synchronization from Dynamics AX. However, some changes are not properly expressed through the Dynamics Publishing API. Microsoft will be addressing these issues in a future hot fix, but if data gets out of sync between AX and Sitecore, please do a full sync in order to get the two environments synchronized properly.