Microsoft Dynamics AX Support

This blog contains posts by the Microsoft Dynamics AX Support teams Worldwide

Upgrade Readiness Errors: Can any of these be ignored?

Upgrade Readiness Errors: Can any of these be ignored?

Rate This
  • Comments 3

The first part of the data upgrade process for Microsoft Dynamics AX 2012 is to run the upgrade checks that attempt to validate the state of your data. These validation checks should be extended by the developers that create all the customizations for the Dynamics AX environment. The process for running these validation checks will create a series of jobs that will run for every company installed on the system, including the DAT company. In most cases the DAT company has been only used for system related tasks with all business data being kept in separate companies, but that is not a hard requirement so some customer data also gets put into the DAT company.

This can cause those customers that do not use the DAT company to see some very unusual errors that come up from the upgrade readiness checks, and it is easy to ask yourself, can I just ignore these or not? The best answer is that some can be ignored, but others cannot, and here are some examples of the most common ones:

Can be safely ignored

  • validateMissingLedgerJournalName - Ledger journal name is missing (you will need to create one later on during data preparation if you skip this step here)
  • projPostingPreValidate - Your Ax2009 system is missing some project ledger posting setup….(this error can be ignored only for companies not using the Project module)

 Need to be addressed

  • validateInventDimBlank - use the Fix button to easily create one
  • Multi Site Activation errors - you will need to activate multi-site within the DAT and every company which means you will need to create a site and warehouse which can be removed later.
  • validateDataAreaIds - Invalid DataAreaId found in some tables - this error is meant to let you know that there is data in a table with a DataAreaId of a specific company where the table should only show records from a virtual company. While it may not be necessary in all cases to clean this up, it would be in your best interest to address this now.
  • validateCompanyInfo - There are company records without a name or country/region - the name and Country/Region ID are required values.

Any other messages that refer to invalid countries, missing LedgerTable or LedgerDimension records, etc. should always be addressed.

Thanks to the commenter who submitted this question originally, please feel free to add comments or reply directly with other questions that would benefit the community.

Kevin Kidder

Leave a Comment
  • Please add 4 and 7 and type the answer here:
  • Post
  • Hi Kevin,

    Thanks for the post !

    I'm trying to run of the upgrade readiness of my customer environment in AX4, and we bumped into this "special" message:

    "The following Sales orders of the type Returned item should be invoice updated before you begin the process of upgrading. For each order ensure the full quantity of all lines are invoice updated"

    Do you know if this kind of message can be ignored as well?

    Because I don't really know how to fix this... :-p

    As the preprocessing will run on live production, there are many chances that salesorders will be created, delivered, invoiced during this step.

    Do I take a big risk by letting this message unfixed?

    Thanks for your time!

    Nicolas

  • Nicolas - the Sales Order type "Returned Item" is one that isn't used by many people, but the validation message is shown to make you aware that there may be issues after upgrading if you have delivered goods but don't fully invoice an order of the Returned Item sales type. AX 2009 (and subsequently AX 2012) added a ReturnStatus field and other returns related fields and tables, and the upgrade scripts that run in the AX 2012 environment do processing to set these fields.

    If the sales order of type Returned Item is in a partially delivered state, then there may be issues with the data after it is upgraded. Looking at the upgrade code, it looks like it should work if the order is in its original Open Order stage, so that part of the validation check might be misleading. You will want to fully test all aspects of any Returned Item orders as part of your upgrade testing as you look at the upgraded AX 2012 data to make sure they can still be processed in every way that you use them in your business.

    Kevin

  • Kevin - Thanks for you answer! We'll go pass through this error and see what it looks like in AX2012 :)

    Nicolas

Page 1 of 1 (3 items)