XSLT or XML interest link

http://www.topxml.com/
http://www.altova.com/mapforce.html

How to use XSLT in AIF and what’s wrong with empty xml Nodes

http://axstart.spaces.live.com/Blog/cns!E82F2C8CB173C0A0!302.entry


he AIF framework is able to communicate with XML messages to the outer world. However there is a small limitation. The format of this XML message should sometimes be altered for this outside world. Microsoft BizTalk can be a solution, when messages are send to different parties and every party has his own XML layout, but when this message has to be send to just one party XSLT can help you out.

XSLT is a mechanism that can rebuild an XML message to a different format (XML to XML or XML to xHTML).

It is possible in AX to use XSLT (BASIC\SETUP\AIF\XSLT Repository. You can use these XSLT in the Endpoint Actions Pipeline Components. The XSLT in AX can only transform the body node of the XML message.

You can test the default AX XML and your XSLT in AX using form tutorial_XSL

Cannot resolve collation conflict for equal to operation

http://www.marcopipino.it/sql/collation-conflict.php

Default Cube Advisor Tool for Microsoft Dynamics AX 2009

http://blogs.msdn.com/emeadaxsupport/archive/2009/04/29/default-cube-advisor-tool-for-microsoft-dynamics-ax-2009-has-been-released.aspx

Integrating a Third Party Version Control System into Microsoft Dynamics AX 2009

https://mbs.microsoft.com/partnersource/deployment/documentation/whitepapers/ax2009_integratingthirdpartyvcs.htm

All about Virtualization....

http://www.virtualizationadmin.com/

Error executing code: Insufficient memory to run script - AIF, Reverse Engineering Tool, ect

In Dynamics AX 4.0 or Dynamics AX 2009 it can happen that a lengthy operation terminates with the following error message in the InfoLog:

Error executing code: Insufficient memory to run script.
A typical example that can result in this error message is when you are running the Reverse Engineering Tool of Dynamics AX 4.0 SP1. Another very common situation is when you are trying to process very large AIF messages with several thousand lines within AX or within an application that uses the Business Connector like the AX BizTalk Adapter.

With Dynamics AX 4.0 a new mechanism was introduced to limit the maximum amount of memory that can be allocated by variables (in X++ code) in a session. This maximum amount is set to 10 MB by default. For some operations like large AIF messages (that are stored in memory during processing) this is however not enough and so the operation is terminated when the maximum amount is reached.



http://blogs.msdn.com/emeadaxsupport/archive/2009/06/15/error-executing-code-insufficient-memory-to-run-script.aspx