Hello Friends,
On last week i am working on one of my domestic customer's database upgrade from Dynamics NAV 2013 to NAV 2016 Indian Version.
It was very nice experience.
Do you believe that - Microsoft has forgot include upgrade codeunit objects in local toolkit.
I had got it from global toolkit folder and update for Indian localization tables and at the end of the day i had got success after solving so many issue.
Following are steps to upgrade database from NAV 2013 to NAV 2016 IN Version
Sr No.
|
Detail
|
Time (Hr)
|
Remarks
|
1
|
For NAV2013/2013 R2 database If a
company name includes a special character, an error may display during the
upgrade. In
this context, special characters include the following:
[ ~ @ # $ % & * ( ) . ! % +/ = ? ]
|
2
|
Check all companies available in
database. And Rename the company by going to
File à Company à Rename
|
2
|
Import 2 Report Objects from Hotfix
Download to avoid conversion issue of report from NAV 2013 to NAV 2016
|
0.1
|
Get it from attachment download link
|
3
|
In Object Designer, verify that no
objects are locked
|
0.1
|
|
4
|
On the Tools menu, choose Build
Server Application Objects, and then choose the Yes
button
|
0.1
|
Make sure that all objects are
in compile mode and delete unwanted – 90 thousand series objects if any.
|
5
|
Upload the Microsoft Dynamics NAV
2016 Partner license to the database
|
0.1
|
Developer Licence - Save In Database
Option
|
6
|
Stop Navision Service If any pointing
to Database and close all sessions
|
0.1
|
|
7
|
Clear all Microsoft Dynamics NAV
Server instance records from the dbo. Server Instance
table in the database on SQL Server
|
0.1
|
Using the SQL Mgt studio clear
server instance table
|
8
|
Create a full SQL backup of the old
database on SQL Server.
|
2
|
(Optional step)
|
9
|
Close the NAV 2013 Development Env
and Close SQM Mgt Studio
|
0.1
|
|
10
|
Open NAV 2016 Dev Env by Run As
Administrator
|
0.1
|
Remember to open as Administrator
|
11
|
Select NAV 2013 Database to Convert
to NAV 2016
|
0.5
|
|
12
|
Connect a Microsoft Dynamics NAV 2016
Server instance to the converted
database. Open the converted database in NAV 2016 and select the service from
File à Database à Information
|
0.1
|
|
13
|
Set the Require Compatibility level
from SQL Mgt Studio
|
0.1
|
SQL Server 2012 - it is 110
|
14
|
Check the minimum require space on
database server for sync tenant process
|
0.1
|
If your database is 50 GB than
minimum 125 GB Require free on database server
|
15
|
Increase the SQL Command Timeout
setting for the Microsoft Dynamics NAV Server instance.
|
0.1
|
Update it to 30 min to 8 hr
|
16
|
Run the schema synchronization to
complete the database conversion
From the development environment:
Open development environment as an administrator. On the Tools menu, choose
Sync. Schema For All Tables, and then choose With Validation and follow the
schema synchronization instructions.
From the Microsoft Dynamics NAV 2016 Administration Shell:
Open the Microsoft Dynamics NAV 2016 Administration Shell as an
administrator,
and then run SyncNavTenant
cmdlet as follows:
SyncNavTenant
–ServerInstance <ServerInstanceName>
*Replace <ServerInstanceName> with the name of the Microsoft Dynamics
NAV
Server instance that is connected to the database.
|
2
|
Run
the NAV 2016 Administration Shell as Administrator and run following command
Sync-NavTenant dynamicsnav90b45778-03
It is failed for some un compile object. Compile all object from developer environment
- fix the compile error of any and then run schema sync from developer or PowerShell.
it will work
Build Server Application Object successfully - it should be complete.
|
17
|
Run any object to check schema sync properly.
Than after delete all object except table
|
0.1
|
delete all object from NAV 2016 -
except tables
|
18
|
Import merge application objects to
the converted database.
When you import the FOB file, if you experience metadata conflicts, use the
Import Worksheet to handle these conflicts.
Finally, on the dialog box for selecting the schema synchronization, set the
Synchronize Schema option to Later.
|
0.2
|
Import objects with later Option.
Make sure that Merge Object contain Upgrade Toolkit Object
in it.
|
19
|
Increase the Size of field 16361
"Sub. Comp. Location" in Item Tables in merged objects before
import to NAV 2016 database
|
0.1
|
Config with standard field copy mode
so I have increase the size of field in merge database
|
20
|
Import the Upgrade Toolkit Objects
with Synchronize Schema option to Later.
|
0.1
|
With later Option (if it is exists in
your merged object in step 17 than it is not require)
|
21
|
Run the Sync. Schema For All Tables –
With Validation option from the
development environment
OR
Run the SyncNavTenant
cmdlet from the Microsoft Dynamics NAV 2016
Administration Shell.
|
2
|
Run the NAV 2016 Administration Shell
as Administrator and run following command
Sync-NavTenant dynamicsnav90b45778-03
it should be completed with no error. If any error exists than solve It
before start data upgrade
|
22
|
Run the data upgrade process
|
2
|
Run it from Developer Env By - Tools
--> DayaUpgrade --> Start with
Default option
|
23
|
Import Merged Role & Permission
|
0.5
|
Using XMLPort Import Permission
|
Note - Do not use upgrade toolkit objects provide in "Local Objects" folder in DVD of NAV 2016 IN Version.
Following error will occur at objects sync steps:
This error has come because of there is no upgrade codeunit exists in toolkit database that will transfer the data in buffer tables.
So i have modified my self the upgrade toolkit objects.
Microsoft has reduce the size of some of the Indian localization fields like:
- Vendor Location (from Code 20 to 10)
- Location Code (from Code 20 to 10)
- etc
We have setup Table Sync Mode = Check for Indian localization database table to avoid this issue.
I have added following code in upgrade toolkit objects.
Download the updated toolkit other objects at following link:
Click Here to Download
I hope it will help you in future
Please write the comment if you find any issue in upgrade.
Thank you
Keep Sharing...Keep Growing....
