If you are working with older Dynamics NAV versions you need to handle the old fashioned objects by using fob or txt files.
Powershell is very powerful and if you need to split a big txt file full of objects, you can use or powershell script:
If you are working with older Dynamics NAV versions you need to handle the old fashioned objects by using fob or txt files.
Powershell is very powerful and if you need to split a big txt file full of objects, you can use or powershell script:
Last week, I was asked if there is any way to convert C/AL objects to .al format. Perhaps there have been more upgrade cases recently, this is a good thing. So today I’d like to talk briefly about this topic in this post.
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.
In this video I show an example of how to reuse old NAV code in Microsoft Dynamics 365 Business Central.
This is the second part of the blog post “Organizing Code for a Seamless Transition from C/AL to Extensions in AL”, where we walk you through some of the steps you can take to organize the code in the existing C/AL coding language before the transition.
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.