Skip to main content

NAV 2013 Upgrade Part II - Upgrading the Standard Objects.

Hi all,

As discussed in previous post about upgrading the customized objects, let's move ahead and see how to upgrade the standard objects.

As the old standard process of Upgrade suggested by Microsoft, we need to compare and merge the changes in target. Lets see the steps for the same.

The steps listed below may not be followed by all during upgrade but for me i find these steps the best way to upgrade which do leave any issues.


Steps -

1) From the client database extract information about the base version used.
    There are certain steps how we can find them -
    1- After opening the database we can see the application version used to open the database and the base
         version of the database, which normally remain same if client have not upgraded the executable. see                
         the highlighted part in below image.


    Form the image its clear that the database version is 2009 SP1 but the exe is upgraded to NAV 2009 R2.

    2 - Extract all objects list to excel and find the hotfix applied on the database using version tag. This is not
         maintained after NAV 2009 but in previous version like 4, 5 you will see the version tag is normally
        appended after a hotfix release.

2) Create a base version from the information collected in step 1, and extract all objects as txt.

3) Extract all client objects as txt.

4) Import them in Navision Developer Toolkit.

5) Compare objects and merge differences manually.

6) If you are in NAV 6 / 6SP1 / 6R2 and  merging to 2013 then merge form differences to pages.

7) If you are in NAV 6 / 6SP1 / 6R2 and  merging to 2013 then merge report classic differences to RDLC Format.

8) If reports are in RTC and you are lucky then just import the report in NAV 2013 and From tools select Upgrade report. May be report get upgraded.

9) For all data ports create XMLPORT.

In Next post we will discuss about data upgrade.

Till Then Enjoy Diwali with your family :).

Regards,
Saurav Dhyani
http://saurav-nav.blogspot.com

Comments

  1. This comment has been removed by the author.

    ReplyDelete
  2. Thanks for sharing the information. Waiting for your blog about Data Upgrade.

    ReplyDelete
  3. How do i import the standard tables to nav 2013?

    ReplyDelete
    Replies
    1. Hi,

      Which standard Tables you want to Import and why?
      YOU SHOULD NOT IMPORT ANY STANDARD OBJECTS DURING UPGRADE.

      For Standard Tables merge the customization by comparing the customized table to the Old Base table.

      Regards,
      Saurav Dhyani

      Delete

Post a Comment

Popular posts from this blog

Microsoft Dynamics NAV 2016 - How to Configure Phone Client.

Hi All, In this article we will discuss how we can connect Microsoft Dynamics NAV 2016 with New Client Launched i.e. Phone Client. This Article Contain Steps for a Android Phone as I have Only Android Phone. I am doing it having all tiers on my windows 8 machine, steps remain same for multiple servers but issues might be different. What we Need (Other what we discuss in this article) -  The Service Tier should be on Public IP . Some of the Data-card does not Provide you Public IP. check it for sure.

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.

🚀 Exploring Vibe Coding with GitHub Copilot for Business Central.

Hi All, In a recent #BCOpenDiscussion session, we delved into the fascinating concept of Vibe Coding —a new way of building software where developers collaborate with AI (like GitHub Copilot) to co-create solutions.  The session covered practical setup, how AI understands context, and even touched on Microsoft's new Model Context Protocol (MCP) integration for enhanced learning. Let’s break down the journey, step by step.