Public Release Note - D365 Finance and Operations Order History Connector 1

1 Introduction

The Order History Microservice is used to transfer order information from Microsoft Dynamics 365 to Intershop Commerce Management (ICM).

This document provides important product information, including version information and dependencies. It also outlines the basic setup and configuration steps.

1.1 References

1.2 Version Information and Dependencies

Intershop Commerce ManagementMicrosoft Order Submission Microservice
7.10.0.0 - 7.10.6.11.0.0
7.10.7.32.0.0

The source code can be downloaded from https://repository.intershop.de//mvn-orderhistory-releases/.

2 Setup

The order history connector is implemented as Microservice.

To familiarize yourself with the concepts, please refer to Overview - Microservices and Overview - Service Registration and Discovery.

Setup instructions can be found at Cookbook - Microservice Deployment and Cookbook - Eureka Deployment and ICM Configuration.

3 Configuration

Following configuration data has to be provided to Order History Microservice. Currently the properties have to be specified in a file that is within the Java classpath of the Microservice.

3.1 Azure Active Directory Credentials Configuration

Configuration for getting an access token from Azure Active Directory (AAD) necessary for OData access to Microsoft Dynamics 365 for Finance and Operations:

# Azure Active Directory credentials
intershop.orderhistory.azure.resource=
intershop.orderhistory.azure.tenant=
intershop.orderhistory.azure.clientID=
intershop.orderhistory.azure.clientSecret=
intershop.orderhistory.azure.token.requestURL=
intershop.orderhistory.azure.token.minimumTTL=

3.2 Concurrency Configuration

Configuration for the number of threads used to process requests from ICM:

# Concurrency configuration
#intershop.orderhistory.threadPool.size=

3.3 Payment Methods Mapping Configuration

How the methods of payment in Microsoft Dynamics 365 are mapped to Intershop payment methods can be extended and adjusted in the file environment.properties.

Configuration for mapping of ICM payment methods to related ones specified in Microsoft Dynamics 365 for Finance and Operation's Contoso demo:

# Payment method mapping configuration
# pattern: intershop.orderhistory.mapping.payment.method.<dyn365-name>=<icm-name>
Example
intershop.orderhistory.mapping.payment.method.ELECTRONIC=ISH_INVOICE
intershop.orderhistory.mapping.payment.method.CASH_DELIV=ISH_CASH_ON_DELIVERY
intershop.orderhistory.mapping.payment.method.CASH_ADV=ISH_CASH_IN_ADVANC
  

The referenced payment methods have to be created and configured before in Dynamics 365 and ICM.

3.4 Managed Service Configuration

In order to connect the Order History Microservice with the ICM, a managed order history service has to be configured.

Note

The microservice allows configuration of one Dynamics 365 tenant. If this maps to one ICM sales channel, create the managed service at channel level.

If multiple sales channels (within one ICM organization) are connected to the same Dynamics 365 tenant, you can also create the managed service at organization level and enable sharing.

To create a service configuration (set technical configuration):

  1. Go to the Commerce Management application: Sales Organization | Services.
  2. Create a new service configuration for the order history service (and enable sharing).
  3. Set the order history service specific settings:
    • Microservice URI e.g., Eureka service URI 'service://orderHistory'.


4 Feature Overview

All orders of a customer will be displayed in the order list in the My Account section.

FeatureDisplayedAdditional Notes
List Viewx
Detail View

5 Limitations

  • Standard Microsoft Dynamics 365 is used for the mapping.
  • All users of a customers can see all orders of the customer in the My Account section. No user order list view is available.
  • Order details will not be displayed in the My Account section.
  • Order Totals cannot currently be displayed without executing a job in the Dynamics back-office first (job "Calculate sales totals"). Before this job is triggered, all totals will be displayed as 0.

6 Known Issues

7 Changelog

7.1 Version 2.0.0

  • Renaming of several attributes of resource objects in ICM backend API.

7.2 Version 1.0.0

  • Initial version


Disclaimer

The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.

Customer Support
Knowledge Base
Product Resources
Support Tickets