Upgrade to AX 2012 R2 or R3 – a few tricks

Share on linkedin
LinkedIn
Share on twitter
Twitter
Share on facebook
Facebook

During the process of upgrade I experienced few interesting things that I would like to share. The whole process with the detail steps is explained on this link.

Removing DMF model from PROD

The first thing is related to removing DMF models from production before you start the upgrade. This is written in the document but in my opinion is not emphasized enough. So, if you have installed DMF you have to remove all models from FPK layer that starts with DMF, after that move model store and data from production to development or test environment where the upgrade will be performed. If this is not done, object conflicts will came up in synchronization.

Baseline database

In the process of installing database component if the upgrade on R3 is in progress there is a field for entering baseline database. This field should be left blank. When you reach the step where system should create a project with code conflicts, possible errors would show up if AX client is not communicating with baseline database. You will receive an empty project. If this happens, server configuration should be checked. It is possible that AX did not automatically populated baseline database name. AX is automatically creating a database with the format of name: _UpgradeR3Baseline. If this is not specified in server configuration, it should be entered.

Upgrading SSRS reports

For the reports that are not customized system will not have any issues, those reports should just be deployed and everything will work as expected. The reports that are customized will not be upgraded that easily. AX will edit rdl files and add comments to let you know where is your code, original code and upgraded code. It will behave as if this is any other object, for example class or table. So, in order to resolve this the process would be:

  1. export xpo with customized report
  2. edit XML code, remove all comments, remove all unnecessary code
  3. import XPO
  4. do this for all customized layers

This process can take very long depending on the number of modified reports. Workaround in this situation could be:

  1. export non-upgraded report from non-upgraded environment (for example PROD)
  2. open rdl file in any text editor
  3. change the version, if you are upgrading from R2 to R3, find the attribute version Version = 6.2.0.0 and change to Version = 6.3.0.0
  4. import in upgraded environment

This should be done for each customized report. This is possible only if it is acceptable to have the same reports as on earlier version. Also, this should be done very carefully and detail testing should be done to make sure that everything is working with new version of code.

During the upgrade client is not showing anything

It is possible that during the upgrade in one point your client does not show anything, there is no menu, you cannot select the company… This is not something that should be investigated in that moment, because when the whole process is completed, the client will work as usual. This is usually happening if client is restarted before code check list is completed. It is possible to access this check list from development mode, from menus/system administration/setup/check lists.

Web services

After installing web services component and starting the AX service in inbound ports, it is possible that service will still not work. In this case web.config file should be checked and if the version is not updated that should be done manually.

You Might Also Like:

Leave a Reply