Since the Application dependency is now implicit (not part of the Dependencies property in App.json but as separate property "Application"), it is not reported as part of the output of Get-NAVAppInfo as a dependency. It means, there is no info about which Application version is supported by given app version. This makes problems in CI/CD when development is done for different versions. In most cases, CI/CD is using Highest dependency policy when using nuget packages, but it leads to situations, when some app is already upgraded to support e.g. newest BC version, but the pipeline is running for some older version (e.g. version of the customer's environment). The pipeline will fail because it cannot install this latest application, because it depends on newer base Application.

Adding the Application dependency into dependencies will help us to create correct nuget packages and filter them based on the supported base Application to only these versions, which are compatible. This will be more critical even for development for SaaS, because if Customer's will not be "pushed" to install Cumulative Updates, we can easily be cough in this trap.

Category: Development
Needs Votes
Ideas Administrator

Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team



In general, it is about correct package generation (e.g. nuget) with correct dependencies to be able to use standard tools how to find correct version of dependencies for some app, including limitation to supported base Application.

Category: Development