BizTalk 2010 Dynamics AX 2012 - Errors in the guidance document

February 21, 2012 · 1 min read

Working though the white paper Microsoft Dynamics® AX 2012: Using Microsoft BizTalk Server 2010 to exchange documents with Microsoft Dynamics AX I came across an issue with incorrect information in the guidance given relating to some of the namespaces used:

1. On page 19 the document states:

"In the Properties pane, enter the Default Value for the sales order create operation:

http://schemas.microsoft.com/**Microsoft** Dynamics/2008/01/services/SalesOrderService/create"

This is incorrect and the namespace used should be:

"http://schemas.microsoft.com/**d**__**ynamics**/2008/01/services/SalesOrderService/create"

You can see this to be correct if you look at the schema that you have extracted from AX 2012 when creating the inbound FILE port.

2. On page 31 the document states:

"In the WCF-NetTcp Transport Properties dialog box, replace the default address with the address for the AIF integration port. For example:

net.tcp://Your_AOS_Name:8201/Microsoft DynamicsAx/Services/TCPSalesOrderRead"

This is incorrect and the namespace used should be:

"net.tcp://Your_AOS_Name:8201/DynamicsAx/Services/TCPSalesOrderRead"

You can see this to be correct if you look at the URI that is displayed when you create the inbound NetTcp port.

3. On page 31 the document states:

"In the SOAP Action header text box, enter the following action string:

http://schemas.microsoft.com/**Microsoft** Dynamics/2008/01/services/SalesOrderService/read"

This is incorrect and the namespace used should be:

"http://schemas.microsoft.com/**dynamics**/2008/01/services/SalesOrderService/read"

This article is part of the GWB Archives. Original Author: Stuart Brierley

New on Geeks with Blogs

  • We Won The One Award I Actually Care About

    Full Scale made the Inc. 5000 for the fifth year straight, the 12th listing across my three companies. Here is why the one award you cannot buy is worth stopping for.

  • Your Customers Build the Features Now

    I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.

  • Get the Size of a Directory in Linux the Easy Way

    du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

  • Vim Search and Replace: The Ultimate Guide

    One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.