Options

Problem when upgrading database with disabled fields

AGrayAGray 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.
Sign In or Register to comment.