Skip to main content

Upgrade analysis using Lifecycle Services (LCS) [AX 2012]

The nature of software is that you will have to upgrade or implement at some point. Dynamics AX is no different from any other software system out there. With Microsoft working hard on Lifecycle Services (LCS) site, doing an upgrade analysis has gotten a lot easier. Below is a diagram illustrating the process to produce your analysis report (Excel file).

Below are steps on how to use LCS to produce the upgrade analysis file.

1. Go to LCS site (

2. Create a new project and click on the Upgrade analysis


3. Enter the project name and select the AX version. Currently in the list there are 2009 SP1 and AX4SP2.

Before you click on the Create button. Make sure to click on the Download link to download the Rapid Data Collector tool.


4. Now that you have created your project, go and install the Rapid Data Collector (do not run against your production – take a copy).

5. Install the Rapid Data Collector and it should be a simple executable that you can run.


6. Once you run it you will get the dialog below. Enter the database server and database name. Accept the agreement and click Collect Data.

This will produce a zip file with the collected stats. Such as table data, usage data, security data. This may take 20minutes for a small one to hours for a large layer.


6. Now back on LCS follow the wizard from step 3 and upload the *.aod file and the Rapid data collection zip file.


7. Click on the Analyse button on the bottom right hand. You can leave it and come back whenever to see it complete.

You should see an excel file that you can download.


8. The excel file will have details on what objects have been modified.


Stats on affected objects, stats on data usage etc.


You can use this as the basis of your upgrade estimate. Estimates are always part science and part experience.


Popular posts from this blog

AX - How to use Map and MapEnumerator

Similar to Set class, Map class allows you to associate one value (the key) with another value. Both the key and value can be any valid X++ type, including objects. The types of the key and the value are specified in the declaration of the map. The way in which maps are implemented means that access to the values is very fast. Below is a sample code that sets and retrieves values from a map. static void checkItemNameAliasDuplicate(Args _args) { inventTable inventTable; Map map; MapEnumerator mapEnumerator; NameAlias nameAlias; int counter = 0; ; map = new Map(Types::String, Types::Integer); //store into map while select inventTable { nameAlias = inventTable.NameAlias; if (!map.exists(nameAlias)) { map.insert(nameAlias, 1); } else { map.insert(nameAlias, map.lookup(nameAlias) + 1); } } //retrieve fro

AX - How to use Set and SetEnumerator

The Set class is used for the storage and retrieval of data from a collection in which the values of the elements contained are unique and serve as the key values according to which the data is automatically ordered. You can create a set of primitive data types or complex data types such as a Class, Record or Container. Below is sample of a set of records. static void _Set(Args _args) {     CustTable       custTable;     Set             set = new Set(Types::Record);     SetEnumerator   setEnumerator;     ;     while select custTable     {         if (custTable && !         {             set.add(custTable);         }     }     if (!set.empty())     {         setEnumerator = set.getEnumerator();         setEnumerator.reset();         while (setEnumerator.moveNext())         {             custTable = setEnumerator.current();             info(strfmt("Customer: %1",custTable.AccountNum));         }     } } Common mistake when creating a set of recIds

Import document handling (attachment) files #MSDyn365FO

Out of the box you have limited data entities for migrating attachments. If you search what is already in the AOT, you will see a few various examples. I suggest you look at the LedgerJournalAttachmentsEntity as it is the simplest and cleans to copy from. I wont go into detail but I will give a quick run down of what it looks like. Use the DocuRefEntity as your main datasource. It does most of the work for you. Set your table you want to import for as the child datasource Add the Key You will need to add the postLoad method. There is minor code to update the virtual field FileContents. Below is an export I did for the general journal attachments. The import zip structure should be the same way. It will create the usual artifacts such as the excel, manifest and package header xml files. You will see a Resources folder under that. If you drill down to the resources you will see the attachments. This is an export and it used the document GUID for uniqueness. The other thing is the extensi