web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

Introducing our New Video Series: Community Spotlight
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Dynamics AX 2012 R2 Da...
Microsoft Dynamics AX (Archived)

Dynamics AX 2012 R2 Data Upgrade Missing Table Mappings

(0) ShareShare
ReportReport
Posted on by Kenny Saelen Microsoft Employee

When executing the step to create the table mappings / field mappings between the source and target system, I see that upgrade scripts are working because there are no mapping errors anymore on the custom tables.

But, when I look at the list of tables (7) that do generate missing table mapping errors, I only see standard tables like CompanyInfo. Looked at the SQL dictionary table (also the DEL_SQLDictiory and the source and target table id's did not change, neither the names. So why does the system not recognize these mappings?

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Kevin Kidder Profile Picture
    Kevin Kidder Microsoft Employee on at

    Kenny - the mapping is done on a table by table, and then field by field basis. You should be able to see what field errors are causing the table mapping errors through that same window. The most common reason is that a field was added to the table in the previous version, and that same field doesn't exist in the AX 2012 code. Typically we recommend leaving the field in the table and renaming it with a DEL_ prefix and associating the SysDeletedObjects60 config key so that the mapping has a place to put those extra fields which might not be used any more.

    Kevin

  • Kenny Saelen Profile Picture
    Kenny Saelen Microsoft Employee on at

    Thank you for your response Kevin. True, the tables and fields are in the ReleaseUpdateBulkCopyTable and ReleaseUpdateBulkCopyField tables. I have used the DEL_ for a few of the fields that move to other fields and added the new fields of AX2012 to the Shadow tables. The scripts then transform the values in the shadow tables and the old fields are begin omitted from the bulk copy.

    I did just noticed something: I started out with a new empty DB to start a test run of the migration. (Until now I was doing stuff in the environment where I actually create the scripts) And because I started with the "register db for upgrade" now, I don't have those table mapping errors now. Same code, same source database, only the upgrade flag is different.

  • Kenny Saelen Profile Picture
    Kenny Saelen Microsoft Employee on at

    Also I saw in the SQLDictionary that due to some unclear reason, the tableid column contained 4103 instead of 41 and it was because for some reason, the tableid was a concatenation of the first 3 columns (tableid, fieldid, array). Using the "register database for upgrade" did not manifest this issue.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Introducing our New Video Series: Community Spotlight

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Sanhthosh.Kumar.K Profile Picture

Sanhthosh.Kumar.K 2

#2
Raed Salah Bzour Profile Picture

Raed Salah Bzour 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans