Skip to main content

Microsoft Dynamics NAV 2016 Extensions - Remove My Extension From Database.

Hi All,

Let's start it from where we left in Last Post.

Recap - "We have Created Cancel Order Extension. Published It and Installed It on the Cronus Demo Database."

If you are not following the Extension Series Then Refer the Table of Contents For Extensions.

In This Article we will discuss How can we remove these extension From the Customer Database.



There are two things that we can do with an Extension Package -
 > Un-install - Disable the Extension So that User Cannot Access or Use It.
 > Un-Publish - Completely Remove the Extension From the Database.

1. Let's Open Powershell and Load navision Module - 
---------------------------------------------------
Set-ExecutionPolicy RemoteSigned
Import-Module 'C:\Program Files (x86)\Microsoft Dynamics NAV\90\RoleTailored Client\NavModelTools.ps1'
---------------------------------------------------

2. Search for CmdLet Uninstall-NAVApp and assign values for parameters -
Name - CancelOrder(Navx Package Name.)
ServerInstance - ExtensionDemo2
** If you don't want data to be archived then Select DoNotSaveData.



Run the Cmdlet and the package will be un-installed.

3. For Un-publishing Navx Package From Database Search for Cmdlet - Unpublish-NAVApp and assign parameters as below -
Name - CancelOrder(Navx Package Name.)
ServerInstance - ExtensionDemo2



Run the Cmdlet and the Extension is now completely Removed From System.

You can download the cmdlets from My Skydrive Folder.

SKYDRIVE LINK

File Name - Microsoft Dynamics NAV 2016 - Extensions Demo (Part 4 Remove My Extension From Database)

** Remember you can run these cmdlets without any change if you are following the Folder structure and File Name as discussed in the Series of the article.

Hope you like the article. Please put your suggestion or queries as comment to article.

Regards,
+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    ---------------------------

RTC Report It is not possible to instantiate the Visual Studio bridge.

Hi all, As a Navision developers I have Multiple Versions of Navision running in single Machine. As discussed Earlier in the post how to run multiple Version of RTC in single machine. So my machine have following details for RTC Versions - NAV 2009 R2    - is installed. NAV 2009 SP1  - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 SP1 IN\ NAV 2009         - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 IN\ This approach has been working great for execution of Classic and RTC Clients. However, after installing Dynamics NAV 2009 R2, if i tried to view the Layout for an NAV 2009 SP1 Report i was getting the following error: ---------------------------  Microsoft Dynamics NAV Classic  ---------------------------  It is not possible to instantiate  the Visual Studio bridge.  ---------------------------  OK    --------------------------- After searchi...

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.