Saurav Dhyani - #MSDynNAV & #MSDyn365bc

Hi Readers, I am fixing this issue in multiple NAV 2018 projects, so I thought it would be nice for sharing it to the community so if anyone faces issues can fix it. Below are the details of what objects are impacted for this change and what additional steps to do other than object merge.

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.

Hi Readers, I think most of us know this but someone asked me and I also did it for one of my customers. I thought it makes sense to have a small blog post for same so that I can reference it later too. When we start Microsoft Dynamics NAV / Business Central it auto start with a company. In this article, we will discuss how we can set a default company in both clients.

Hi All, Microsoft Have Released Cumulative Update for October 2018. Please find below the details of Cumulative Updates Released for Microsoft Dynamics NAV 2015, NAV 2016, NAV 2017 & NAV 2018. Below are the Links to Download the Latest Cumulative Update.