Saurav Dhyani - #MSDynNAV & #MSDyn365bc

Hi Readers, I hope you all are following this series and learned something new with this series. If you haven't read any article in this series then Please Refer Table of Index . First, I thank you for all your suggestions, comments and Questions. Your engagement with this series kept me motivated to keep writing about this. I am always open to your suggestion about articles that you would like to see in this blog. Use Contact Us Page and let me know your suggestions for future Post.

Hi Readers, As discussed in the Last article, in this post we will develop the Expense Analysis Report as per our Customer Requirements. If you are new to this series then Please Refer Table of Index . In this article, we will develop a New Report for Expense Customization / Feature that we build during this series.

Hi Readers, As discussed in the Last article, in this post we will Test for all development done in this series. If you are new to this series then Please Refer Table of Index . We will break our Test in multiple Test Cases to test all subscribers that we have developed in our Functionality. Let's Test our solution.

Hi Readers, As discussed in the Last article, in this post we will continue with our Customer Requirements. If you are new to this series then Please Refer Table of Index . In this article, we will discuss adding custom code in base objects and what is the Futuristic way of adding code. In your customer are Pre-2018 then you can use Hooks for those instances. (Refer Old articles to check how to use Hooks).

Hi Readers, Last article we Understand what are Trigger Events. As promised in this post we will understand if you are doing development in Pre-NAV 2016 Database. If you are new to this series then Please Refer Table of Index . With this article, We will understand about HOOKS and Use Hooks for development. This will help Developers to develop with keeping in mind about the future and all code can be easily transported to the future when your customer plan to Upgrade. Let's discuss that in details.

Hi Readers, Last article we unboxed Database Trigger Events. As promised in this post we will understand Page Trigger Events in Base C/AL Code. If you are new to this series then - Please Refer Table of Index . With this article, I will try to clarify all doubts and questions about  Page Trigger Events. This will help Developers to subscribe to Page Trigger Events. Let's discuss that in details.

Hi Readers, Last article we subscribed a Trigger Events. As promised in this post we will understand Database Trigger Events in Base C/AL Code. If you are new to this series then Please Refer Table of Index . With this article, I will try to clarify all doubts and questions about  Database Trigger Events. This will help Developers to subscribe to Database Trigger Events. Let's discuss that in details.

Hi Readers, As discussed in the Last article, in this post we will continue with our Customer Requirements. If you are new to this series then Please Refer Table of Index . In this article, we will discuss adding custom code in base objects and what is the Futuristic way of adding code.  In your customer are Pre-2018 then you can use Hooks for those instances.

Hi Readers, Last article we Understand what is Integration Events. As promised in this post we will understand if you don't find an event because you are not in Latest Version of NAV/Business Central or you are in a version which does not support Events (Pre-NAV 2016). If you are new to this series then Please Refer Table of Index . With this article, We will understand about HOOKS and Use Hooks for development. This will help Developers to develop with keeping in mind about future and all code can be easily transported to future when your customer plan to Upgrade. Let's discuss that in details.

Hi All, Microsoft Have Released Cumulative Update for February 2019. 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.