Stuart Brierley

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/dynamics/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"

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 when a Dynamics 2012 inbound port was attempting to consume a file created by a BizTalk 2012 send port.

Initially the error given was that Dynamics could not access the folder specified.  Giving the Dynamics user in question permisions on the folder led to a follow on issue where Dynamics could not consume the file as it was not the file owner - this was because the file had been created by and was owned by the BizTalk Host Service account.

To fix this issue without changing any permissions on the folders or files, you need to add the domain account that the BizTalk host runs under to Dynamics AX with administror privilages.

Dynamics will then be able to consume the files that are created by BizTalk send ports.

I have recently started a new project where we will be integrating a large number of systems with Dynamics AX 2012 using BizTalk Server 2010.

We are working alongside consultants from both PWC and Microsoft and it is apparent that there is not a great deal of experience or information out there regarding Dynamics AX 2012 integration, nevermind specifically using BizTalk 2010!

To that end I thought I would make some notes on the lumps and bumps along the road to integrating Dynamics AX 2012.

So far I have the following two posts:

BizTalk 2010 Dynamics AX 2012 - Error when consuming a file

BizTalk 2010 Dynamics AX 2012 - Errors in the guidance document