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 Application_x.x.x.x.app
    • Microsoft_System Application_x.x.x.x.app
    • Microsoft_System_x.x.x.x.app
With these changes 
  • You will get one more additional symbol for Microsoft_Application_x.x.x.x.app  

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.


Regards,
Saurav Dhyani

Labels:
Location: House No. 1, Shivlok Colony, 2, near Himalayan Academy Post Office, Shivlok Colony, Sewla Kalan, Majra, Dehradun, Uttarakhand 248171, India

Comments

Post a Comment

Popular posts from this blog

Microsoft Dynamics NAV 2016 - How to Configure Phone Client.

Hi All, In this article we will discuss how we can connect Microsoft Dynamics NAV 2016 with New Client Launched i.e. Phone Client. This Article Contain Steps for a Android Phone as I have Only Android Phone. I am doing it having all tiers on my windows 8 machine, steps remain same for multiple servers but issues might be different. What we Need (Other what we discuss in this article) -  The Service Tier should be on Public IP . Some of the Data-card does not Provide you Public IP. check it for sure.
28 comments
Read Complete Article »

How to Set Up NavUserPassword Authentication in Business Central.

Hi Readers, In this article we will discuss steps to Setup NAVUserPassword in Business Central on-prem. NavUserPassword is an authentication method that's handled by Business Central Server, but isn't based on Windows users or Active Directory. Each user is set up with a username and password that's configured inside Business Central only. The user is prompted for username/password credentials when they start the client. #msdyn365bc, #credentialtype
1 comment
Read Complete 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.
21 comments
Read Complete Article »