Generate table mappings

  • Article

Important

This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

The Generate table mappings task in the Data upgrade checklist creates the mapping between the tables and fields in the Microsoft Dynamics AX source database and the tables and fields that were created in the Microsoft Dynamics AX 2012 database during the Create tables step in the Data upgrade checklist.

Before you start the Generate table mappings task, you must complete the Data upgrade checklist steps Connect to source database and Create tables. If any errors were generated in the Create tables step, you must fix them before you proceed with mapping the tables and fields, otherwise the mapping will be incorrect.

Generate table and field mappings

To generate mapping between tables and fields in the source and target databases, perform the following steps:

  1. In the Data upgrade checklist, click Generate table mappings.

    The upgrade framework begins the mapping process and, when mapping is complete, opens the Table mapping between source and target systems form. This form provides separate tabs where you can see all the tables and fields from the source database and how they are mapped to tables and fields in the target database. You can also view a list of the extended data types that are used in the source fields and have been brought into the target database.

  2. Review the mapping on the Tables and Fields tabs in the form and note any errors.

  3. Address mapping errors and rerun the Generate table mappings step.

Important

  • If you encounter a mapping error, you may need to implement a presynchronization script that defines a mapping for the source table and field. For more information, see the white paper How to write upgrade scripts in Microsoft Dynamics AX 2012.

  • Customized solutions will frequently cause table mapping errors. For example, the addition of a new extended data type will create an error for every table where it occurs. You will not be able to complete upgrade until you write and implement presynchronization scripts to address schema differences you have introduced.

  • For testing purposes, it is possible to perform an upgrade on the non-customized portions of your installation and to ignore failed, customized tables using the Continue button on the Table mapping between source and target systems form. The affected tables will not be copied, but the rest of the upgrade can proceed.

  • You cannot proceed to the next Data upgrade checklist step, Generate upgrade task prioritization, until you address any errors in table and field mapping. If you do, data upgrade on the target system will fail.

Mapping errors

You may encounter the following table-mapping errors for tables that are listed on the Tables tab in the Table mapping between source and target systems form.

Status

Description

OK

Mapping for the table is complete without error.

No mapping defined

Mapping has not been created because no applicable metadata was found in the Microsoft Dynamics AX 2012 database.

Field error

An error has occurred that resulted in a source field not being mapped to a target field. The error could be that there is an inconsistency in the field data type, no field to import, or a string-length difference in the field name.

You can see which fields have errors on the Fields tab.

Mapping conflict

Two source-database tables are mapped to the same target table. You must resolve the conflict by renaming the table or assigning it a different ID.

Waiting on source

A source table is still being used in preprocessing on the Microsoft Dynamics AX source system.

Target table not empty

The table that was created in the Microsoft Dynamics AX 2012 target database has data in it. The source data cannot be copied into a table that already contains data. Clear all data from the target table.