In this video, I look at how to compare different data types in AL. I also discovered an obscure, but interesting difference between AL and C/AL, read more below the video.
Since Business Central 2019 release wave 2 (version 15), the application has become completely AL-based. All functionality that modifies standard business logic must be moved into an Extension. This change influences how upgrades are performed and impacts all the solutions that are still in C/AL, making Dynamics partners consider transitioning to Extensions in AL
In this article, we will discuss Upgrading a database to Business Central Wave 2 from Business Central Spring 2019 Release (14.x).
This all is for a Business Central Spring Database that does not include any C/AL Code Customization. The database can only include Third Party and Custom Extensions.
My session at NAV Tech Days this year was together with Nikola Kukrika and we did an end 2 end walk-through of how to upgrade a code customized C/AL solution in 14.x to 15.x (AL), converting the code, upgrading the data, explaining all the pitfalls and in some cases, how to cope with missing functionality.
When you’re developing in C/AL in Business Central/NAV 2018, you might run into this issue: You want to edit the code in an object through the Developer Environment, and the Application automatically crashes or closes without displaying an error message. This occurs when you open a Codeunit or click on C/AL editor in a Page/Table, and it occurs only when you are designing the object and go to C/AL code by hitting F9.