Inside Dynamics AX

During a data upgrade from AX2009 to AX 2012 R3 we face an issue during UnitOfMeasure Upgrade script in AX 2012 Upgrade check list . The error message was as below: No upgrade script was registered for the table <TableName> field <FieldName>(relation <RelationName>). Register an appropriate upgrade script or add the relation to the exclusion list. The info Log generated is as below: After investigating this issue I came to know that the issue was due to Some Custom Tables Which Were having relation with UnitOfMeasure Table and their relation were not added to the exclusion list, and when the script run it add the Relations to the exclusion list for other Standard tables which can be seen in Class "UnitOfMeasureUpgradeValidator" method "registerExcludedrelations". Adding the custom Code to this method resolved the issue :-)

During data upgrade the mapping algorithm follows the following precedence for source and target table mapping: 1. Check special mapping – this is custom mapping as defined within pre-synchronize scripts 2. Try to map by name, e.g. SalesLine -> SalesLine (Salesline table exist on both source and target system) 3. Try map by DEL_ prefix, e.g. SalesLine -> DEL_SalesLine (salesline table on traget doesn’t exist but DEL_Salesline table exists) 4. Try to map by ID (Salesline or DEL_salesline table on target doesn’t exist but the ID of the Salesline table on source and target is same) 5. Otherwise, mapping error is reported and must be fixed!

Some times during Upgrades we face a compilation error  “Table does not contain a valid time state key. A unique index needs to be marked as a valid time state key.” Cause The index is disabled using  indexAllowDup  method, then properties  AlternateKey  and  ValidTimeStateKey  are reset to default value  No . ReleaseUpdateDB:: indexAllowDup ( new  DictIndex( tableNum (TableName), indexNum (TableName, DateEffectiveIndex))); The error starts to show up then indexes are not enabled correctly using method indexAllowNoDup : ReleaseUpdateDB:: indexAllowNoDup ( new  DictIndex( tableNum (TableName), indexNum (TableName, DateEffectiveIndex))); AlternateKey  and  ValidTimeStateKey  properties are not set using the code and then you start getting compilation error mentioned above. Solution You should use the method  indexAllowNoDupAndDateEffective  instead: ReleaseUpdateDB:: indexAllow...

In this post I will be introducing to the Microsoft Dynamics AX 2012 Data Upgrade, tasks involved in the Data Upgrade process along with some key points which must be considered before and during the upgrade process. Before getting started I would first like to introduce you to few key terminologies which will be used throughout the series of these posts:  Microsoft Dynamics AX 2012 Data Upgrade can be divided into two categories:   In-place upgrade   Upgrade from Older version i.e. AX 4.0 or AX 2009 Term In-place upgrade is referred to the upgrade from one version of Microsoft Dynamics AX 2012 to another i.e. AX 2012 R2 to AX 2012 R3. This type of upgrade requires no source-to-target workflow that is used when we upgrade from AX 4.0 or AX 2009. In this post and further upcoming post we will be focusing on the Data upgrade in AX 2012 from older versions i.e. AX 4.0 or AX 2009 which follows the source-to-target model. What is Source-To-Target M...