Skip to main content

Microsoft Dynamics NAV 2016 Extensions - Concept Behind Extensions.

Hi All,

In this article Let's See what is the Concept Behind Extension which is Released with Microsoft Dynamics NAV 2016.

Consider a Scenario that you are a Developer of your Favourite Software Solution. For Example I will consider Jet Reports, I am a Developer with Jet Reports Team.

Now I Start the Software Development of Top of Say Window 8.1. Now Software Development is Over and I need to Pack the Solution and Release it for My Customers and Partners.



What I Should Ship?

 My Software With Operating System? (Complete Package)  --- Black Line

 OR

Only Part That I have Developed with Some Dependencies and Pre-requisites. -- Green Line


Yes we all know that We only Receive the Solution Without Operating System. (That is Green One)

So When I Release My Software as a Installer I Release An Executable With

 > Some Pre-requisites  
   - Windows 8.1
   - 32 / 64 Bit OS
   - Office 2013

 > Some Dependencies -
    - DotNet Framework

Any Customer / Partner want to use my Software need to meet the Requirement that My Solution Have & Should have all Dependencies in The System.

When a Customer Install My Software All Required Changes are Applied and My Solution is Ready to be Used.

If Customer Doesn't Like the Software He/She Can Go Ahead and Un-install the Software and Every Related Data From His System will be Removed During Software Removal Process.

What we do with Microsoft Dynamics NAV When we Release our Customization To Customers - 
 > Yes We Ship the Whole Solution as Fob (My Software with Operating System)

With Extension, We will be able to Release Our Solutions (Customizations) as a Application with Pre-Requisites and Dependencies.

What we do with Microsoft Dynamics NAV For Install And Un-Install The Customization ?
 > We Merge Application Objects During Installation.
 > We Remove New Objects & Remove Custom Fields From Customer Database During Un-Install.

With Extensions, Customer Can Add Or Remove the Customization Like a Software Solution. Same Like Software Un-install All Relevant Data related to that Customization will also get removed from Microsoft Dynamics NAV.

Sounds Cool! If Yes Then Stay Connected and Keep Reading.

Thanks & Regard,
Saurav Dhyani
saurav-nav.blogspot.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.