Table mapping between source and target systems (form)

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

Click System administration > Setup > Checklists > Data upgrade checklist. Click Generate table mappings.

This form attempts to map tables and fields from your Microsoft Dynamics AX source system database to target tables and fields in the target database. The results are displayed so that you can resolve any errors that occur. You can rerun the form as many times as necessary until the mapping completes successfully.

Warning

Do not rerun mapping once you have performed the Launch data upgrade task. This will corrupt the mapping and lead to failure of bulk copy and other operations.

Tasks that use this form

Generate table mappings

The following tables provide descriptions for the controls in this form.

Tabs

Tab

Description

Tables

Displays the mapping between source and target tables, source and target fields within the tables, and mapping status and errors.

Extended data types

List of extended data types used in the source fields and copied to the target database.

Grid columns

Column

Description

Status

Status of the table- and field-mapping attempt for each table. Possible values are as follows:

  1. OK: The source is correctly mapped to target and no user action is required.

  2. No mapping defined: There is no corresponding target system table or field. This means that the mapping algorithm attempted name-to-name, DEL_<table name>, and ID-to-ID correlations and failed in each case.

  3. Field errors: The source-to-target mapping is missing and an error must be resolved. The resolution could be not to copy the table, or to map tables by implementing a presynchronization script. For more information, see the white paper How to Write Data Upgrade Scripts for Microsoft Dynamics AX 2012.

  4. Mapping conflict: The same field is mapped twice. This error must be resolved.

  5. Target table not empty: The target table contains data. By default, the source table data will not be copied into a non-empty target table. This is the correct behavior for all Microsoft-shipped tables. For customized tables that are not empty, write a presynchronization script to truncate the table or to merge the data between the source and target tables. For more information, see the white paper How to Write Data Upgrade Scripts for Microsoft Dynamics AX 2012.

  6. System: This is a mapping between system tables.

Field errors

Number of fields in the source table that could not be mapped to fields in the target table.

Source table name

Table name in the source database.

Source table ID

Table ID in the source database.

Target table name

Corresponding table name in the target database.

Target table ID

Corresponding table ID in the target database.

Source field name

Name of a field in the source database that will be mapped to a field in the target database.

Target field name

Name of the target database field to which a source database field was mapped.

Extended data type ID

IDs of extended data types used in the source fields and copied to the target database.

Extended data type name

Names of extended data types used in the source fields and copied to the target database.

Buttons

Button

Description

Rerun

Initiate a new attempt to map tables. Use this this to regenerate the mapping after you have corrected errors. This operation wipes out the old mapping.

Continue

Click this button to continue with table mapping despite an error in a table. Tables with errors will not be copied to target system.

Close

Close the form.

Important

If you close the form before you have resolved all table and field mapping errors, you will not be able to proceed to the next task in the Data upgrade checklist.

Fields

Field

Description

Show all mappings

When this field is selected, all mappings will be displayed, including ones with a status of OK or System.

Announcements: To see known issues and recent fixes, use Issue search in Microsoft Dynamics Lifecycle Services (LCS).