Skip to main content

#msdyn365bc - How Do I Install New Version of Extension (on-Prem)?

Hi Readers,

In this article we will discuss about installing a new version of extension on-prem & docker containers.

With Extension model, when we change apps that we build for our customers, there are certain steps to be followed for Installation of new version of app in tenant.

This is based on a question that received on email. You will need to follow steps in same order when there a new version of Per Tenant Extension (PTE) or ISV/Apps on-Prem version.

For this demo, I will build an app called "Upgrade Extension Demo".

1. Assuming that version 1 of app is installed in the tenant as shown below.

2. A table which is part of the extension also have data as shown below.

3. Adding a new feature in app. During addition of that feature I also updated the app version to 2.0 (as shown below).

4. To Publish to new version of app we will have to running following PowerShell command in this order.

  • Un-install old app.
  • Publish New app.
  • Sync New app.
  • App Data upgrade.
  • Unpublish old app.

For Reference - 

Uninstall app - Does not remove data from the tenant.

For the Demo I am using docker environment so commands are bit different then local environment.

Docker Commands (as shown below) - 

  • Uninstall-BcContainerApp
  • Publish-BcContainerApp
  • Sycn-BcContainerApp
  • Start-BcContainerAppDataUpgrade
  • Unpublish-BcContainerApp

5. After all commands are executed, we will see Version 2 of app available in tenant.

6. Let's check the data in the table. As we can see below data is still exist in table with a new field added.

If you are using on-Prem server then commands are (after loading module) - 

  • Uninstall-NavApp -ServerInstance Servicename -Name AppName
  • Publish-NavApp -ServerInstance Servicename -Path NewAppPath
  • Sync-NavApp -ServerInstance Servicename -Version AppNewVersion -Name AppName
  • Start-NavAppDataUpgrade -ServerInstance Servicename -Version AppNewVersion -Name AppName
  • Unpublish-NavApp -ServerInstance Servicename -Version AppOldVersion -Name AppName

Hope this article helps you for installing new version of Apps.

Let me know your views as comment to article.

Saurav Dhyani


  1. Thank youn Saurav, I think in last screen shot, a small correction required, in Sync NavApp command, it should have the new App name not the one which get uninstall

    1. In my Scenario the new and old app name is same.
      If you have changed the name then you should change the name in publish, sync and install commands.


Post a Comment

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.