Integration release notes

Microsoft Dynamics 365 CO

Supported Source System Version

Microsoft Dynamics 365 for Finance and Operations and Commerce.

Download the software

To download and install the software, get the latest .zip file from the Indirect Tax Customer Center:

Open the Indirect Tax Customer Center at https://customercenter.sabrix.com/.

Find Integration for Microsoft Dynamics 365 F&O
and C&O
(if applicable) for the latest version in the Available Products list, and verify that Installed Version
is set to None
.

Select Download for Integration for Microsoft Dynamics 365 F&O
and C&O
for your version.

Save the file.

Unzip the Microsoft Dynamics 365 F&O and C&O (if applicable) file.

How to Install IDT for D365 Commerce

ONESOURCE IDT for D365 Commerce was built with the Contoso demo data. As such, a full retail deployable package would include the Contoso retail store front example which is not needed or desired.

Instead, a trimmed down package is provided with only the files needed for repackaging in a full retail deployable package. More details are available in Microsoft's article: Create deployable packages.

Install F&O Package

First install the F&O package for ONESOURCE IDT. Apply the package to a development environment and check-in all the files added. For more information use either of the instructions here:

Manage third-party models and runtime packages by using source control

Including ISV Binaries in Your Package (codecrib.com)

Merge ONESOURCE IDT Commerce into the local RetailSDK

Copy all the DLLs from

<IDTRetailPackage Extract Location>\References

to the

RetailSDK\References

folder.

Copy all the SQL files from

<IDTRetailPackage Extract Location>\Database\Upgrade\Custom

to the local

RetailSDK\References

folder

(Optional) Application Insights is an Azure service with the capability to host logs that are generated while running Commerce Runtime code. If a ONESOURCE tax integration log cannot be written to the channel database, it can instead log it to an Application Insight. To configure this,

First create an Application Insights in your Azure subscription. After creating an App Insight on the

Go to the

Overview

page, find the GUID called an Instrumentation Key
in the Essentials area.

Add this value to the ext.AppInsightsKey
node in the CommerceRuntime.Ext.config
file. If you want to find traces that are generated upon exceptions follow these directions: Log extension events to Application Insights

Copy and paste the Add
lines from the

<IDTRetailPackage Extract Location>\Assets\CommerceRuntime.Ext.config

file into the local

RetailSDK\Assets\ CommerceRuntime.Ext.config

(Optional) Copy the Application Insight Instrumentation Key
from Step 3, to the ext.AppInsightsKey
node.

Copy and paste the ItemGroup
lines from the

<IDTRetailPackage Extract Location>\ BuildTools\Customization.settings

file into the local

RetailSDK\ BuildTools\Customization.settings

file .

Check-in all new and updated files.

Run your pipeline(s) to build new F&O and Commerce (Retail) packages.