Skip to main content

Microsoft Dynamics NAV 2016 Extensions - Publish & Install An Extension.

Hi All,

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

Recap - "We understand Concept of Extension Using an Example of Shipping of Jet Report Solutions. Later We did a customization on a Standard NAV 2016 W1 Database For Cancel Order Using Events. After That We Created an Manifest File for our Extension. Finally we were able to Create the Navx Package for Our Extension."

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

In This Article we will see how we can publish & Install the Extension in our Customer Database, which in this case is a Standard Cronus NAV 2016 W1 Database.



We will be Deploying the Extension on the Extension_Demo2 Database which we created Earlier. Let's Not waste Time and start the Demo.

** Publish Means That the Extension is in the System but Not active for Usage.
** Install Means That the Extension is active and can be used for by the users.

A system can have multiple published Extension but the User can use only those who are installed.

Prerequisite -
> A Service Should be Mapped & Running to Our Extension_Demo2 Database Named as ExtesnionDemo2.

1. Lets Start Powershell and Load Navision Module using Cmdlet -
-------------------------------------------------------
Set-ExecutionPolicy RemoteSigned
Import-Module 'C:\Program Files (x86)\Microsoft Dynamics NAV\90\RoleTailored Client\NavModelTools.ps1'
-------------------------------------------------------

2. Search for Cmdlet - Publish-NAVApp, and assign parameters value as below - 
Path - C:\Extensions\CancelOrder.Navx  (Path of the Package)
ServerInstance - ExtensionDemo2 (Service Mapped To Extension_Demo2 Database)
------------------------------------------------------
Publish-NAVApp -Path C:\Extensions\CancelOrder.Navx -ServerInstance ExtensionDemo2
------------------------------------------------------



3. After Execution of Above cmdlet, the Package will be Published on the Database Mapped to Service Instance.

4. You can check all Published Package on the Database Using Cmdlet - Get-NAVAppInfo
--------------------------------------------------------
Get-NAVAppInfo -ServerInstance ExtensionDemo2
--------------------------------------------------------

5. Now The Next Part is to install the Navx Package on the Customer Database. Search for Cmdlet - Install-NAVApp.

Assign Parameter Values as Below -
Name - CancelOrder (Navx Package Name)
ServerInstance - ExtensionDemo2 (Service Name Mapped to Extension_Demo2 Database)
------------------------------------------------------
Install-NAVApp -Name CancelOrder -ServerInstance ExtensionDemo2
------------------------------------------------------



The Package will now be available for the users to use in Role Tailored Client.

In The Next Article I will clear the doubts that you have if you have completed till here.

You can download the cmdlets from My Skydrive Folder.

SKYDRIVE LINK

File Name - Microsoft Dynamics NAV 2016 - Extensions Demo (Part 3 Publish & Install An Extension)

** Remember you can run these cmdlets without any change if you are following the Folder strucuture 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

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 - 

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.

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.