TableSync 'move' fails

EvR
Member Posts: 178
In an updated 2013 (to 2016) database I'm having issues with a table sync upgrade. I've copied the original table to a new temporary table. Removed all code and variables from the new table. All fields are the same and so is the PK (even ran a text compare to confirm).
By my upgrade CU is throwing this error:
Any suggestions?
By my upgrade CU is throwing this error:
Sync-NAVTenant : When the TableSynchSetup.Mode::Move mode is used in an upgrade codeunit for synchronizing a table, the structure of the upgrad e table must match the original table. The fields and the primary key of the upgrade table must match those in the original table. The following errors must be fixed: The definition of the upgrade table 'UPG-Extended Text Line' must match the definition of the old table 'Extended Text Line'. Upgrade table 'UPG-Extended Text Line' cannot have fields which have a different design in the original table 'Extended Text Line': 'Text'. At line:1 char:1
[TableSyncSetup] TableSyncSetup(VAR TableSynchSetup : Record "Table Synch. Setup") DataUpgradeMgt.SetTableSyncSetup(DATABASE::"Extended Text Line",70500,TableSynchSetup.Mode::Move);
Any suggestions?
0
Answers
-
Can you please check if all the fields in upgrade table 'UPG-Extended Text Line' have same data types, field length when compared to original table.0
-
Yes they are. Like I said, I even ran a text compare of the 2 tables.0
-
Hi EvR,
Open your Upgrade table again in the dev environment, and save it with sync mode force.
Then check your call to SetTableSyncSetup if the two table ID fields are correct.
Then try again.0 -
I found different primary keys for UPG Custom Report Layout(int) and Custom Report Layout(code).
then I modified UPG Custom Report Layout primary key to code and force compiled. I got the below error in syncNAVTenant.
Is there any solution for this?
Sync-NAVTenant : Changes to the tenant database could not be applied. Affected tables will not be available.
The first error was:
When the TableSynchSetup.Mode::Move mode is used in an upgrade codeunit for synchronizing a table, the structure of the upgrade table must match the
original table. The fields and the primary key of the upgrade table must match those in the original table.
The following errors must be fixed:
The definition of the upgrade table 'UPG Custom Report Layout' must match the definition of the old table 'Custom Report Layout'.
Data in the fields 'ID' in the original table 'Custom Report Layout' cannot be saved in the upgrade table 'UPG Custom Report Layout'. Please make sure
that listed fields are present in the upgrade table and they match equivalent fields in the original table in terms of their design.
Original table 'Custom Report Layout' cannot have fields which do not exist in the upgrade table 'UPG Custom Report Layout': 'ID'.
The upgrade table UPG Custom Report Layout cannot have fields that do not exist in the original table, Custom Report Layout. The following fields are
not allowed: Code.
0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions