Upgrade the application code.
Exporting all objects from the new customized Microsoft Dynamics NAV 2015 database to an objects.fob file.
Convert the database by opening it in the Microsoft Dynamics NAV 2015 development environment.
Prepare the data for the upgrade.
- Make sure that you are the only user connected to the database.
- Back up the database and save the backup file in a safe location.
- Make a copy of the customer’s database in SQL Server Management Studio. You will upgrade the copy and keep the original.
- Identify a User ID and password for a superuser in the system or create a new superuser that you can use for the upgrade process. Log in as the superuser when you perform the upgrade.
- Verify that you have the dbcreator and securityadmin Server Roles for the Microsoft Dynamics NAV SQL Server instance by using SQL Server Management Studio. To manage companies, objects, and licenses in a Microsoft Dynamics NAV database you must also have the db_owner database permission.
- Disable integration properties for the database.
- Open the database in the Microsoft Dynamics NAV 2015 development environment.
- Run a database test to determine the state of the customer’s database.
- Run the Adjust Cost – Item Entries batch job to make sure that the inventory cost data in the customer’s database is up to date.
- For each company in the database that posts inventory costs to the Microsoft Dynamics NAV general ledger, run the Post Inventory Cost to G/L batch job.
Import the Upgrade Step 1 objects, and then perform Step 1 data conversion.
Export permission sets and permissions.
Delete all objects except tables.
Import the customized objects from the objects.fob file.
Import the objects for upgrade step 2, and then perform Step 2 data conversion.
Import upgraded permission sets and permissions.
Initialize all companies.
Delete obsolete tables.
Delete the upgrade toolkit objects.
Test the database.
I don’t see the step 1 and step 2 fobs in the local objects folder for 2013R2 to 2015. There is one fob for Upgrade700800.US.fob (2013 to 2015) and One fob for Upgrade710800.US.fob (2013R2 to 2015). Am I missing something here?
i have the same problem, can anybody help us?
thanks