All good things come in threes, as they say. So here is 3. Codeunit 50000: OnRun() ShipMethod.INIT; ShipMethod.INSERT; ShipMethod.INSERT; // This duplicate statement has been put here intentionally Codeunit 50001: OnRun() IF CODEUNIT.RUN(50000) THEN MESSAGE('OK') ELSE MESSAGE('LASTERRORTEXT: %1', GETLASTERRORTEXT); First "from the bare head", but test it in NAV! Both in classic and RTC. For the latter: easiest: run codeunit 50001 from NAV 2013 DE on NAV 2009: you have to create…

There has been quite some fuzz about the NAV 2013 partner licenses. Especially about the missing ISV Insert Rights. On one of my previous posts Gary Winter commented that this omission was "a bug in the licensing tool that does not allow partners to download a 2013 license with insert rights." Since then I have been checking VOICE frequently to see if the bug was fixed already, but to no avail. Apparently I did not check for some weeks until today to find out that it has been fixed so that…

Just to spread the news I am copying Simon Ejsing's announcement on mibuso : simonejsing Post subject: Test Toolset for NAV 2013 - 9000 tests for free Posted: Mon Nov 05, 2012 2:31 pm As announced at Directions US 2012, Microsoft recently released the Application Test Toolset for Microsoft Dynamics NAV 2013 at PartnerSource. The supplement is applicable to the following country releases of Microsoft Dynamics…

This last item in my NAV2013 Beta to RTM - Some Striking Code Changes series is addressing code changes NAV core team made to get IF-THEN-ELSE statements coding standards compliant. If you read the Microsoft Dynamics NAV 2009 Developer and IT Pro Documentation on IF-THEN-ELSE , and also on the use of parentheses , you'll notice that there are quite some conventions to take into account. Quite some to violate, isn't it? Let's take some exemplar code changes that underline these conventions…

Although the coding standards are unambiguous about the layout of CASE statements , there has always been practiced an alternative flavor. Both within MS and outside. This is the standard syntax: CASE <Expression> OF <Value set 1>: <Statement 1>; <Value set 2>: <Statement 2>; ... ... <Value set n>: <Statement n>; END; And this is the alternative flavor: CASE <Expression> OF <Value set 1>: <Statement 1>; <Value set 2>: <Statement 2>; ... ..…