What do you do to future-proof your apps, and do you sleep when at night when Microsoft rolls out new versions of Business Central? In this video I take a look at why one of my apps didn’t work on v21, check it out:
One of the things that can be really annoying in Dynamics NAV or Business Central is the dependent apps.
What are dependent apps?
Some partners have made a base app that will contain all the basic functionality, that they use with all customers. Then they create apps that can be added to the solution but basing the solution on some data or functionality from the base app.
Probably most of you already know that with the Dynamics 365 Business Central 2019 Wave 2 release, we have the ability to modify the Base App. But to extract Dynamics 365 Business Central Base App as .al files that would compile might be quite difficult. As you have probably noticed, picture/image functionality on Docker is becoming outdated in Business Central 365 latest releases.
I was working on a report in Microsoft Dynamics 365 Business Central recently, and the client wanted the report to show a value from an extension that was not a dependency for my customizations app. Because I am lazy efficient, I did not want to go to the trouble of adding an entire separate app as a dependency just to get a single field onto one report. Adding dependencies is a lot of work and requires future maintenance, and it just wasn’t worth it.
There are a lot of very useful repositories out there with useful apps and information for Business Central. Unfortunately, it is hard to keep track of all of them or to even know of the existence of these repositories. For this reason, I decided to create a repository with a readme file that contains many useful repositories.