Skip to main content

All good things (must) come to an end - NAV 2013 and NAV 2013 R2.

Hi Readers,

Yes, it's true and I feel what the title says "all good things (must) come to an end".

I still remember the good days when NAV 2013 & R2 was released and how happy we were. These two versions played a major role in the Product Future and also the existence of Product.

If you were there with NAV at that time, market rumors were that its time to end NAV as it way behind in terms of technology. Everyone was worried and not ready to change when these versions were released.

Last week Microsoft announced End MainStream Support for NAV 2013 and NAV 2013 R2. Read here on Microsoft Blog.

Today when I look back, I still remember all challenges and learnings that these two releases had. We loved them, learned them and grew with them.

Let's try to remember which bring major changes in product and released with these versions -



1.  Dimensions Changes.
I still believe that few developers are still having a hard time with this change, but those who know it in out understand the great impact of it in terms of Record count in the database and also the extraction time for values related to dimension from the database.

2. Web Client.
The First Version of web client and how hard to configure web client and how happy we were to see web client of NAV. We used to show it to all our customers and was so proud of it. Yes, it was not that great in terms of performance as of today but NAV 2013 gave birth to the Web client.

3. Automation was supposed to completely rewritten to DotNet. 
With NAV 2013 Microsoft announced retirement to Automation. It created a lot of problems but we as the community fix most of these problems.

4.  Query. 
A New object was released with NAV 2013, Query which somewhat replicates the behavior of SQL Queries.

5. Bank Account Reconciliation.
😃You killed our major customization with this but yes customers liked it and used it the way we never assumed to be used.

6. Object Changes via Service Tier.
Ah, I was pretty painful to start with I think until CU06 but after that and until today we are using the changes that you (NAV 2013R2) bring to our work.

7. Sigle Signon.
Yes, it was hard to configure but great to use when we use it.!!

8. Multitenant Deployment.
Wow, I still remember how much excited I was when multitenancy was released and I was eager to implement it at a customer site. I still have goosebump when I thought about our first successful implementation and I am sure we will use it in future.

9. Data Upgrade Automation.
All long night steps that need to be run manually were automated with NAV 2013 R2. It was a great help with little pain to start with but every new thing comes with some pain.

10. Help Server.
NAV 2013 R2 was the first version which took client help to next level using a web server. This extended help for the web client.

NAV 2013 & NAV 2013 R2 - We loved you and we will remember you, You were a milestone in the future of NAV. Of Course, you will be Missed!! 😞

My two cents!!

Regards,
Saurav Dhyani
www.sauravdhyani.com

Comments

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

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.