Skip to main content

Future - What Next After NAV 2016. Code Name - Madeira...

Hi All,

While Browsing web I came across some article which says about next release of Microsoft Dynamics NAV.

Let's see the History of Code Names Given to Previous Version  -

NAV 2013 - Code Name 'Sicily'

NAV 2015 - Code Name 'CRETE'

NAV 2016 - Code Name 'CORFU'

And as we all know that all these are the Islands.


Next NAV release will be known as code name ‘Madeira’ and yes that is also a Island.




What will be new in this release? 

Office 365: Further enhanced “in” Office 365 experience
Azure: Pre-packaged Azure ML services
Core Product: Developer experience, More service integrations
Deployment: Fast set up, Easy configuration

Stay Tuned for More..

Regards,
Saurav Dhyani
www.sauravdhyani.com

Comments

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.

How to Set Up NavUserPassword Authentication in Business Central.

Hi Readers, In this article we will discuss steps to Setup NAVUserPassword in Business Central on-prem. NavUserPassword is an authentication method that's handled by Business Central Server, but isn't based on Windows users or Active Directory. Each user is set up with a username and password that's configured inside Business Central only. The user is prompted for username/password credentials when they start the client. #msdyn365bc, #credentialtype

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.