Skip to main content

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 2015-01-11_About_slipstream
Update Installer 2015-01-11_about_update

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 models (each one with the hotfix number).

Slipstream 2015-01-11_model_slipstream
Update Installer 2015-01-11_model_update

When you run the update installer it actually allows you select the specific hotfix to install otherwise you can choose to install all.


If there are any conflicts the next step will show the objects and you can run the impact analysis.


Once you are happy with it you can save the package for use next time.

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

Approve Workflow via email using template placeholders #Dyn365FO

Dynamics 365 for Finance and Operations has placeholders which can be inserted into the instructions. Normally you would want this to show up in the email that is sent. One of the most useful ones is the URL link to the exact record that you are approving. In the workflow configurations use the placeholder and build up your message. Towards the end it has workflow specific ones. The URL token is %Workflow.Link to web% . For the technical people the token is replaced in this class WorkflowDocumentField. This is what I inserted into my email template. <BODY> subject: %subject% <BR> message: %message% <BR> company: %company% <BR> for: %for% <BR> </BODY> Should look like this. The final result looks like this. If you debug these are the place holders that are put together.