I have always preached that you shouldn’t try to keep your Docker containers running. Containers should be something, which easily can be dismissed and recreated for any developer. One of the frequent questions is then: But what about my demo/development data?
During NAV TechDays 2019 there were a lot of sessions that I would describe as “develop Business Central doing minimum development using AL“. Sounds weird? For me yes… at least at the beginning.
Speakers, such as Arend-Jan Kauffmann (https://www.youtube.com/watch?v=cp848e9WBFs), showed how to connect Business Central with Power Apps or use Power Automate (previously named Flow) and our BC. And my first impression was – noooo way it can be so easy.
I think that many of you on your Dynamics NAV or Dynamics 365 Business Central projects have tasks executed by using console applications (.exe) scheduled by using Windows Task Scheduler or other systems. This works good for on-premise environments (just take your .exe application, create a new schedule with Windows Task Scheduler and you’re ready to go), but what about using these .exe applications on a SaaS environment?
So now – “let’s get started” with ..
Why would I rename all my AL-files?
Well – because of Microsoft and their new (upcoming) code analysis rule about file name conventions. You might already have complied with their previous conventions, and … they will change. Even better: they actually already changed .. Just read here:
Probably most of you already know that with the Dynamics 365 Business Central 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, so in this article, we will talk about how to extract the Dynamics 365 Business Central Base App using Docker, Business Central DVD, and symbols. Also, we will briefly mention how to upload a customized Base App.