The issue here is that printing an X++ report to file (pdf) via a business connector call within a web service, the paper size is defaulting to "letter" instead of the usual A4 size we use in Europe, but we'll also explain first how AX finds the default...

The issue we're talking about here is this: There is an AX form which users make their own personalisations to, moving some of the fields around, or perhaps adding other fields (via the right click->setup functions). Then I need to redevelop...

Dynamics Ax Project Server integration make use of Project Server Event Handlers: http://msdn.microsoft.com/en-us/library/ms481079(v=office.12).aspx . The event handlers are used when we create, update or delete integrated Project in Project Server and...

So the issue here is setting a batch job to run with a recurrence of 1 minute in AX2009 - a server bound batch job. The job itself takes just a few seconds but the batch job isn't completing for a few minutes, and so the next run doesn't happen after...

The document attached to this post ("UK VAT Setup Guidelines in AX 2009.PDF") provides a sample setup of Value-Added Tax (VAT) in Microsoft Dynamics AX for the United Kingdom. The document contains illustrations of different transaction scenarios and...

Ever been in a situation where your AOS crashed? And all you had to show for it was a lousy event log message 1000 which didn't tell you anything except that it crashed? Or perhaps you've just wanted to see what your AOS is actually running at a given...

******** Latest update 11-July-2011 ******** Scripts now allow class and table name resolution ******** This post explains how to find the AX user and the X++ call stack that caused an AOS crash - by using special scripts for WinDbg - before reaching...

This post explains how to find the X++ call stack that caused an AOS crash - before reaching this stage you need to first have captured a memory dump, and then set up WinDbg ready to do some analysis, we have posts which explain both of those steps: Capturing...

This post explains how to find the ax user that caused an AOS crash - before reaching this stage you need to first have captured a memory dump, and then set up WinDbg ready to do some analysis, we have posts which explain both of those steps: Capturing...

Once you have collected a dump file, to analyse it you need to use a tool called WinDbg. In this post I am going to explain how to set up WinDbg so it's ready to debug a memory dump taken from a Dynamics AX process. If you're not sure how to create a...