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

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.

NAV 2013 Upgrade Part III - Data Upgrading.

Hi all, As per agenda we need to discuss the data upgrade in NAV 2013. The process is similar to what used to be till NAV 2009 R2 but with some changes. Let's start the process. Remember -  1) You can only upgrade a database to NAV 2013 from NAV 2009 SP1 / R2 SQL Only. 2) The Synchronization of users with SQL Server is no more required.