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 a page with an action that executes codeunit 50001

Note

Variable ShipMethod in codeunit 50000 is linked to the Shipment Method table (10).

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 the ISV Insert Rights can now be configured for your partner license.

Related posts

• On NAV 2013 Licenses - Part 1 | Add-on Ranges
• On NAV 2013 Licenses - Part 2 | Add-on Ranges

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 NAV 2013: W1, AU, CA, DE, DK, ES, FR, GB, IN, IT, MX, NL, NZ, SE and US The supplement contains the following per country: Tools for managing and executing tests, capturing code coverage information, selecting relevant tests out of available tests Between 7,000 – 9,000 real regression tests, giving a wide feature coverage across the application Helper libraries for improving test development through reusing common functionality Searchable documentation of helper libraries with examples of how to use library functionality You can find the download here Any feedback is highly appriciated and will help us focus our efforts better to support your needs!

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. It think it's a good way to refresh your coding standards knowledge, like most of the previous posts in this series could have done that somehow.

1. EXIT or ERROR as last statement in the THEN part of an IF-THEN-ELSE?
    Do not continue with an ELSE statement

Correct

Incorrect

Click on the image to get a full view that's readable.

2. Compound or long expressions after IF?
    THEN should be on a new line and aligned with IF

Correct

Incorrect

Click on the images to get a full view that's readable.

Note

This also applies to the DO part of a WHILE-DO statement

3. Use parentheses only to enclose compound expressions inside compound expressions

I.e. do not use redundant parentheses.

Correct

Incorrect

Click on the images to get a full view that's readable.

Note

This also applies to WHILE-DO and CASE statements

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>;
...
...
  <Value set n>: <Statement n>;
END;

Note that:

• the alternative is only used when the statement following the value set is a single line statement (see also the screen shot)
• I have left out the optional ELSE part for clearness sake.

However, as said, the coding standards are unambiguous about the layout stating:

The action [i.e. the statement - lvanvugt] starts on the line after the value set and is further indented by two character spaces.

Meaning that the alternative flavor is not part of these standards and now with NAV 2013 you could say that has been confirmed by means of the code cleanup performed between Beta and RTM, where all alternative layouts have been revised and changed to the standard layout.

The alternative is more compact, but the standard is more clear in displaying the 'available' value sets.

Click on the images to get a full view that's readable.

Update 20121104

Found another nice example: