Upgrade Toolkit

Format Old Base
Version
Format Current
Custom Version
Transfer
Customizations to
the New Base
Version.
Import
Customizations
3.1 What is Multilanguage?
Database: Old base version, for example Navision Financials 2.60:
1 Export ObjectTime file as described on page 17.
2 Create translation file, translate it into English in Navision Localization Workbench
as described on page 17 and import the translation. Note that this step is only
necessary if your local Microsoft Business Solutions office has not made an English
database available to you.
3 Import object and field names file from new base version as described on page 23.
4 Compile all objects.
5 Import ObjectTime file as described on page 25.
6 Export object file.
7 Convert all objects with conv-ml tool as described on page 26.
8 Remove unique IDs as described on page 34.
Database: Customer’s current database:
1 Export ObjectTime file as described on page 17.
2 Create translation file, translate it into English in Navision Localization Workbench
as described on page 17 and import the translation.
3 Import object and field names file from new base version as described on page 23.
4 Compile all objects.
5 Import ObjectTime file as described on page 25.
6 Export object file. You can choose to only export the objects that you want to
transfer to the new database, but you can also export all objects.
7 Convert all objects with conv-ml tool as described on page 26.
8 Remove unique IDs as described on page 34.
Database: A merge tool:
1 Use a merge tool to merge changes from the old base version and current custom
version files into new base version as described in Chapter 4, Merging on page 37.
2 Export new custom version file.
Database: New base version, Navision 4.0:
1 Import object file that you created during the merge.
13