https://alguidelines.dev/navpatterns/2-anti-patterns/Recent content in 2. Anti-Patterns on AL GuidelinesHugo -- gohugo.ioen-ushttps://alguidelines.dev/navpatterns/2-anti-patterns/nav-upgrade/Mon, 01 Jan 0001 00:00:00 +0000https://alguidelines.dev/navpatterns/2-anti-patterns/nav-upgrade/Anti-Patterns in NAV Upgrade By Carlos Raul Garcia and Bogdana Botez at Microsoft Development Center Copenhagen Context: when NAV is upgraded, whether on-premises or in the cloud, developers have the chance to write upgrade code to move data across changing data structures. Writing good quality code will help successful upgrades. General on upgrade Problem: assuming that the upgrade table contains data. If the table is empty, it means that either the upgrade has run, or there was no data in the original tenant; in both cases, the upgrade code should exit immediately.https://alguidelines.dev/navpatterns/2-anti-patterns/reusable-bugs/Mon, 01 Jan 0001 00:00:00 +0000https://alguidelines.dev/navpatterns/2-anti-patterns/reusable-bugs/By Bogdana Botez, Andreas Moth, Eric Wauters (waldo), Elly Nkya, Nikola Kukrika April 1st, 2015 Abstract It is difficult to come up with new and different bugs in each release, and it is a waste of resources to not use the ones which already had proven successful in the past. To avoid reinventing the wheel, we propose to come up with new innovative ways to create bugs that are reusable and generic enough to be used in various places of the application.