Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 298 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Problem when upgrading database with disabled fields
AGray
Member Posts: 2
Hi all,
I'm currently upgrading a 3.7 Nav database (SQL 2008 R2) to 2009 SP1 (SQL 2008 R2).
Having converted the database to Microsoft Dynamics NAV 2009 SP1, and when importing the new customised objects that I created in the compare and merge process, I'm getting an error that "The Variant Code field on the Bin Content table does not exist in the SQL Server table or view." The Variant Code field is disabled in the 3.7 Bin Content table and was re-enabled as part of the compare and merge process (a significant number of disabled fields on different tables were re-enabled as part of the compare and merge process but this is the first such error that I've come across).
If I set the Variant Code field on the merged table back to disabled and re-import the table in a separate fob, the error isn't raised. I'm just wondering if anyone has come across a similar situation and has a work around that might save me having having to disable all the fields that were re-enabled as part of the merge process.
Thanks for your help.
I'm currently upgrading a 3.7 Nav database (SQL 2008 R2) to 2009 SP1 (SQL 2008 R2).
Having converted the database to Microsoft Dynamics NAV 2009 SP1, and when importing the new customised objects that I created in the compare and merge process, I'm getting an error that "The Variant Code field on the Bin Content table does not exist in the SQL Server table or view." The Variant Code field is disabled in the 3.7 Bin Content table and was re-enabled as part of the compare and merge process (a significant number of disabled fields on different tables were re-enabled as part of the compare and merge process but this is the first such error that I've come across).
If I set the Variant Code field on the merged table back to disabled and re-import the table in a separate fob, the error isn't raised. I'm just wondering if anyone has come across a similar situation and has a work around that might save me having having to disable all the fields that were re-enabled as part of the merge process.
Thanks for your help.
0