Skip to main content


Showing posts from January, 2015

Bringing copy company back [AX 2012]

Back in 2013 I wrote a blog post on how to duplicate a company. I basically summarised Microsoft's guide on MSDN. The big issue with those steps are that it is very manual and can scare a lot of people. Imagine having to copy a company set up for 10 plus companies. This can be very tedious and time consuming. Plus there are some references that have to be set up manually like the journal names voucher series. So, why not automate. I have put my project on codeplex which you can download and use (READ here carefully). User guide Download the class from under source codes tab Import it into your AOT Run the class NAVAX_CopyCompany – Right click Open. From company – Enter the from company id To company – Enter the new company id (if company doesn’t exit it will create it) Use record ID compression – RecIds are recreated and in sequence Release produc

Dynamics AX 2012 Cumulative update 8 Install Explained

With the recent release of AX 2012 cumulative update 8 there has been some considerable changes to the installation. I will try explain a few of the major ones to consider. Before anything you must read the blog post from Microsoft: Download is available on LCS now. We are given 2 choices a slipstream and an update installer. When you run the update installer it will download actual installation files (application models/binary) at the time of installation and you are able to save it the end of the process. Below are screenshot of the About form. Notice the version number difference. Read the blog link for detail – it explains both versions.     Slipstream Update Installer     Below are screenshots of the models installed form. Notice how a slipstream (ie. New installation) contains a single SYP model. On the second screenshot notice how it has installed over 1500 mo

Management reporter - increasing performance

Thanks to a colleague of mine who had gone through this with a large data customer and Microsoft support. When using Management reporter try to separate the SQL instance from the AX database. This is because AX has the best practice of setting the max. degree of parallelisation in SQL server to 1. MR does not deal with this that well, it is recommended to leave it as the default value of 0. Since this setting is at server level. The only solution is to have 2 SQL server instances.