Skip to main content

#msdyn365bc - Clean your app.json file?

Hi Readers,

This article is about a quick change during AL Development.

This change can be implemented starting Business Central 15.3 and higher. 

With Business Central 17 the Visual Studio code automatically apply these setting when you create a new apps. 

As we all understand, that we all extension need to have at least dependent on Microsoft default apps.

Microsoft’s Application app introduced with Dynamics 365 Business Central version 15.3.

This app encapsulates all the dependencies from the System Application and Base Application apps and provides an abstraction to protect AppSource and PTE extensions.

What does that mean?

  • Remove the direct dependencies to the Base Application and System Application.
  • Add the "application" property in the app.json file and provide here the minimum Microsoft Base Application version that your app is compatible with.

Without these changes
  • You will have symbols downloaded for 
    • Microsoft_Base
    • Microsoft_System
With these changes 
  • You will get one more additional symbol for  

You only need to depend from Application and all other dependencies are transparently inherited.

All extensions submitted on AppSource must respect this requirement. 

Please update your app.json file as soon as possible.

Saurav Dhyani


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.