Upgrade 3.6 to NAV 2009

ara3n

What I mean is that you create a new form with source table field.


run the form and filter the form for the 5K range field and copy and paste it in 3.7 database.

You paste it in 3.7 database on the new form that is based on the virtual field table.

Have you copied records from a editable list form from one company to another? Nav inserts the records automatically.

rsaritzky

ara3n wrote:

What I mean is that you create a new form with source table field.
run the form and filter the form for the 5K range field and copy and paste it in 3.7 database.
You paste it in 3.7 database on the new form that is based on the virtual field table.
Have you copied records from a editable list form from one company to another? Nav inserts the records automatically.

OK, thanks.

Yes, I've copied items from one object/company to another - I use that frequently in copying functions from one codeunit or report to another. I just wasn't 100% clear on the technique. No problem building a form in both databases on the Field table (it's already there in fact). Thanks for the clarification.

rsaritzky

OK, here's the steps I did. I'm using the SQL version under SQL2005:

1. Took my 3.60 database, made a copy and opened it under NAV2009
2. Created a form for the "Field" table - included all fields.
3. Created an empty 3.70 database and opened it under NAV2009
4. Copied the form from the 3.60 database into the 3.70 database
5. Opened the 2 databases in 2 separate windows
6. Ran the "Field" form in 3.60, filtered on 50000..59999 and copied
7. Went to the 3.70 database, opened the "Field" form, and pasted.

Received the error message "You must specify the property OptionString for the Vendor Type field.
Type: Option
Table: Vendor

I have a custom field "Vendor Type" defined in the Vendor table. It has a valid OptionString.

ara3n

exclude the options data types, You'll have to copy those field manually by designing the tables and copy and paste them for each table.

anshpat2826

rsaritzky wrote:

OK, here's the steps I did. I'm using the SQL version under SQL2005:

1. Took my 3.60 database, made a copy and opened it under NAV2009
2. Created a form for the "Field" table - included all fields.
3. Created an empty 3.70 database and opened it under NAV2009
4. Copied the form from the 3.60 database into the 3.70 database
5. Opened the 2 databases in 2 separate windows
6. Ran the "Field" form in 3.60, filtered on 50000..59999 and copied
7. Went to the 3.70 database, opened the "Field" form, and pasted.

Received the error message "You must specify the property OptionString for the Vendor Type field.
Type: Option
Table: Vendor

I have a custom field "Vendor Type" defined in the Vendor table. It has a valid OptionString.

Same Problem guys I am also facing same problem.
I am also having same error.

ara3n

read my previous post.

anshpat2826

ara3n wrote:

read my previous post.

already doin that

anshpat2826

how can customer can i get migration tool.?
Or it is only available to partner

ara3n

It's in 2009 dvd.

rsaritzky

anshpat2826 wrote:

Same Problem guys I am also facing same problem.
I am also having same error.

After thinking about it some more, I realized that the technique that Rashed described is a "shortcut", intended to help speed up the process of upgrading from pre-3.70. If you were to do it the "standard" way, you would use the developers toolkit or some other comparison/merge tool to move all the custom fields one table at a time from your pre-3.70 customized database to the 3.70 base database. Since you don't need any trigger code in this step (all your trigger code has to go into the NAV2009 base database), it is an easy "trick" to copy the custom records from the "Field" table instead. The fact that Option fields don't get copied correctly is unfortunate, but it is just a small inconvenience, requiring you to merge them the "standard" way. I only had 6 tables with custom Option fields, so it only took me a few minutes to manally merge them into the 3.70 database before continuing on.

ara3n

by merge you mean you designed the table and copy and pasted the field from one db to the 3.7 db?

andy76

Hello everyone,

but if we should migrate a database of version 3.1ACH Native to NAV 2009 SP1 RTC, the process is possible?Is it similar to that explained before?
Or is it necessary others step?

The customer was managed by another solution partner and at the moment we know nothing of this database. What do you suggest?

Thank you

Andy

ara3n

Yes similar process can be applied from 3.1 as well as as 2.6.

mb6606

Version 3.6 there are 13 Tables that are not in 2009.
Examples:
12- Project
20 - cust./ITem Discount
28 - Item Price
90 -Bom Component
100 - Item Purch Qty. Disc.
99000791 - Production Order
99000792
99000794
99000794
99000809
99000815
99000817
99000819
What is the best way to deal with these missing tables???

ara3n

If you have modification in those table, you need to move them to the correct tables.
For example Project and Department table are now dimensions.


If you have no modifications, delete them. Actually the upgrade toolkit if I remember suppose to delete obsolete tables.