Hi, Can anyone help me around this issue? I am upgrading a Navision database from GB2.60 to GB3.70. I have a problem at step 5 of the “Upgrade of GB versions to GB 3.70” document. Problem: BACS for payment to suppliers is now standard, but I had already implemented similar in customised 2.60 database. So I am allowing 3.70 BACS functionality to replace custom changes, but I cannot import new Vendor table because: I had created column 50000 “BACS Account No.” in GB2.60. I have deleted this column during merge process and hoped (bit daft I know) that the import of the object to new database would would put the data in 10550 “BACS Account No.” because in is in same postition and has same name. The import of the object fails because there are values on records in column 50000. Obviuosly columns resolved by “Field No.” I thought I would try “renaming” 10550 to 50000 in GB3.70 object, then set back to 10550 after import to upgraded database, but my license won’t permit me. So is the only solution… 1. retain column 50000 in merged version so I have both columns in the new object (WITH NAME ALTERED IN ONE OF THEM e.g. 50000 “BACS Account NO. OLD” 2. Import the object to upgrade database 3. Run code unit to move data from 50000 to 10550 4. Delete column 50000 It’s my first upgrade[:I] ! P.s. Compare and merge tool - thought I’d give it a go - NULL POINT!!![:(!] Many errors introduced to base version objects! Hopeless with C/AL code! I am spending a lot of time raising issues with service system. Would have been quicker moving changes manually!
Hello Jon, You cannot create fields in Navison tables between 1 to 49999 for the same reason you cannot create Navision objects in the same range. These are restricted for use in future versions. The only people who can do this are developes at MBS. Your suggestion:
quote:
So is the only solution… 1. retain column 50000 in merged version so I have both columns in the new object (WITH NAME ALTERED IN ONE OF THEM e.g. 50000 “BACS Account NO. OLD” 2. Import the object to upgrade database 3. Run code unit to move data from 50000 to 10550 4. Delete column 50000
Sounds fine to me!
Thanks Edward![:D]