It might seem boring to discuss about this, but passing variables By Value vs By Reference in NAV AL (as in other languages) does not always behave the same (depending on the type of variable). In this post I will explain the differences as this is an important thing to understand. Let’s compare passing a…
DetailsWhen developing Extensions for NAV, using the Modern Development Environment in Visual Studio Code, you cannot use .Net Interoperability. See this link if you want to read more about this subject. So if you have NAV developments that use .Net and you want to move them into Extensions you will probably need to replace the…
DetailsIt is clear that the future of NAV is Visual Studio Code and AL. And to be honest I find more fun and interesting to play with this “smart text editor” compared to the old “development UI” C/Side. Even if at the beginning it seems more difficult because you need to know in what places…
DetailsRecently I got a requirement to increase the length of the comment field (for example in Customers, Vendors, Sales Documents, Contacts etc) as in standard NAV the comments limit is 80 characters per line. We could increase this limit, but the issue is that the maximum length of a text field accepted by NAV is…
DetailsBecause I needed it recently for a unit test, today I will show you how you can validate an XML against a XSD schema in Nav. We have the following XSD schema: And we need to validate the below XML file against it: First, we need to convert ‘False’ into ‘false’ and ‘,’ from decimal…
Details
