In a lot of other programming languages, the concepts of asynchronous calls and background tasks are well established and supported. The idea is to have the ability to kick of something in the background without having to wait for the result and thereby blocking the user.
Last month we wrote about AL Code Management with GIT and how to set up it along with one additional tool named GitExtensions. This month we continue this series with the Remote repository with Azure DevOps and a short guide on how to use GIT in daily development. We hope you will have a good read!
Today, I was working on a new E Foqus product and this is something that needs a fair amount of FactBoxes.
It could be solved using a single FactBox object throughout the system. I started with a C/Side approach, trying to get the information from the parent page into the FactBox with SubPageLink but that didn’t work. I was even trying to be too creative with the new SystemId field.
Probably most of you heard about AL code management with GIT, which is one of the most popular tools for this purpose. As you know, in the previous versions of NAV, you could use GIT, but in most cases, you needed some third party Addin. With AL and Visual studio code, we finally get native integration with GIT. In these two articles series, I‘m going to talk about how to start using these amazing tools.
In standard Microsoft Dynamics 365 Business Central or NAV there is not a “hard-close” for a month-end. However, there are many month-end activities that can be completed. This blog provides a high level of elective processes and tasks for closing period within Business Central or NAV.
When you try to convert existing C/Side objects to AL the first attempts are typically done while scoping OnPrem. This gives an overview of the errors to be fixed w.o things like DotNET.
In this phase you typically switch between C/Side and Visual Studio Code all the time fixing the errors one-by-one and reconverting.
I’ve been fortunate enough to be assigned to a Microsoft Dynamics Business Central implementation, and working in AL has been a whole new world for me. Coming back to Visual Studio and auto-complete after years of being in the old NAV development environment is nice. Years ago, I split my time between ASP.NET/C# development and NAV development, and it’s good to have Intellisense back. I had pretty well forgotten what it was like to have all those fancy bells and whistles after years of toiling in the bare-bones NAV development environment.