Monthly Archives: December 2013

Dynamics AX 2012 Under the Hood – Retail

The Dynamics AX 2012 Under the Hood webinar series is designed to give AXUG members the chance to learn more about Dynamics AX 2012 by taking deep dives into functional and technical areas. Sit back not only hear about the benefits of the latest release of AX, but also see that new functionality in action as each webinar will include a demo review inside Dynamics AX 2012.


Leave a comment

Posted by on December 16, 2013 in Retail


Tags: , , , ,

How to flush AOS cache form code

Flush the AOS cache from code

Under Menu items > Action, duplicate all these 3 menu item actions and three menu action items that can be used to flush system data, the AOD, and dictionary
1. SysFlushAOD
2. SysFlushData
3. SysFlushDictionary

Duplicate these 3 menu action items and give them a new name


These three are running on “Called From” which when we run it on client side, it will clear client cache. We need to be able to clear AOD, sys data and dictionary and cause a refresh, therefore, we need to change it to “Server”

Go to RunOn property and change it from “Run-On” to “Server”


Now, start run each menu action item one by one.

static void DevClearCache(Args _args)
#define.FlushAOD(“DevSysFlushAOD”)                  // replace with your own menuitem name
#define.FlushData(“DevSysFlushData”)                // replace with your own menuitem name
#define.FlushDictionary(“DevSysFlushDictionary”)    // replace with your own menuitem name
Args args = new Args();
MenuFunction mf;

// Flush AOD
mf = new MenuFunction(menuitemActionStr(#FlushAOD), MenuItemType::Action);;

// Flush Data
mf = new MenuFunction(menuitemActionStr(#FlushData), MenuItemType::Action);;
info(“Data has been refreshed”);

// Flush Dictionary
mf = new MenuFunction(menuitemActionStr(#FlushDictionary), MenuItemType::Action);;

You can download the entire project here.


Posted by on December 11, 2013 in Development


Tags: , , , , , ,

Demo Package V4. – Microsoft Dynamics AX 2012 R2 CU7

Dynamics AX 2012 R2 CU7 is available for download on partner source.

If you are a fan of windows 8, there is a special section for Windows 8 Applications for Microsoft Dynamics AX 2012

Windows 8 Applications for Microsoft Dynamics AX 2012 Demo Scripts and Installation Links
Application Name Title Download
Approvals Microsoft Dynamics AX Approvals Demo Script Approvals (docx) 2.21 MB

Windows Store Installation link:
Approvals application

Expenses Microsoft Dynamics AX Expense Demo Script Expenses (docx) 2.75 MB

Windows Store Installation link:
Expenses application

Timesheets Microsoft Dynamics AX Timesheets Demo Script Timesheets (docx) 3.35 MB

Windows Store Installation link:
Timesheets application

Microsoft Dynamics Business Analyzer Microsoft Dynamics AX Business Analyzer demo script for Microsoft Dynamics AX Demo script (pdf) 1.28 MB

Windows Store Installation link:
Microsoft Dynamics Business Analyzer

Leave a comment

Posted by on December 10, 2013 in Installation and Configuration


Tags: , , , , ,

Dynamics AX – How to capture a Crash Dump

If your Microsoft Dynamics AX application ever crashes then you should know what troubleshooting steps to take to find out why this exception has occurred.

Please see the attached videos recorded by one of our Escalation Engineer’s from the Support team.


  1. The first video includes information about; What is a crash?
  2. The second video includes information about; How to collect crash dumps.

 Dynamics AX – How to capture a Crash

Diagnostics Tool:

To capture a crash dump one of the tools used is debug diagnostics 1.2 please see the following link


Tags: , , , , ,

How to deploy all AX2012 reports


There’re 3 different ways to deploy Dynamics AX2012 reports:

  1. Through AOT
    AOT > SSRS Reports > Reports > right click on report > Deploy Element
  2. Through Visual Studio
    Open the report project > Right click on the project or solution node > Deploy
  3. Through PowerShell
    Publish-AXReport -ReportName *

Through AOT

– Go to AOT > SSRS Reports > Reports > (right click on report) > Deploy Element

– Right click on the report node

– Click “Deploy Element”


Deploy AX2012 report through AOT

Through Visual Studio

– Open the report project

– Right click on the project or solution node

– Click “Deploy”


Deploy AX2012 report through Visual Studio

Through PowerShell

– Go to: Start > Administrative Tools > Microsoft Dynamics AX 2012 Management Shell

– Then enter Publish-AXReport -ReportName *

This will deploy all AX2012 reports into report server, you might want to do this after the initial installation as the report server doesn’t have all the report there yet. It takes about 20 minutes for me to deploy all the reports (that’s on my Hyper-V image, if run on better spec server, it could be much faster).

If you want to deploy a specific report, just replace the wildcard (*) with the report name.

Eg. Publish-AXReport -ReportName SalesInvoice

*It is the report name under AOT > SSRS Reports > Reports > SalesInvoice, not the project name under AOT > Visual Studio Projects > Dynamics AX Projects > SalesInvoiceReport


Publish-AXReport -ReportName * will deploy all report (use wildcard to deploy full set of report)


Report deployment in progress


Report deployment in progress


Report deployment in progress


Report deployment completed


1 Comment

Posted by on December 10, 2013 in Development


Tags: , , , , , ,

Label does not update after updating a hotfix

When I installed CU7 to my Ax2012R2 environment,  label did not update correctly and this bothered me so much. What I did to fix this is

  1. Stop the AOS
  2. Navigate to C:\Program Files\Microsoft Dynamics AX\50\Application\Appl\[Instance Name].
  3. Delete all *.ald files. The ALD files “Application Label Data”
  4. Start the AOS







Posted by on December 4, 2013 in Installation and Configuration


Tags: , , , ,

AOS Environment Name in Developer Workspace

One of my colleagues found this interesting piece of information today and I would like to share

Often when we want to see what AOS we are connected to we turn on ‘Show AOS Name’ in Tools->Options->Status Bar.


Then we see the AOS Name in the status bar:


The only problem is that is not necessarily the AOS name.  This is just the name given to the AOS in the config file (.axc).  If we look at the .axc in notepad there is a line for this name and we can change it here:


And see the change in the AX status bar:


So if the .axc was created incorrectly using the status bar to identify the AOS could be dangerous.  It would probably be a better idea to always check the port number in the .axc file and compare it to the configurations listed in the server configuration utility.


Tags: , , ,

%d bloggers like this: