Contrary to the other run-able CSIDE objects – i.e. Page, Report and XMLport – we can run a Codeunit and catch the result from this execution: TRUE or FALSE Syntax: [Ok :=] Codeunit.RUN(Number[, Record]) So if we call CODEUNIT.RUN and request a return value, as illustrated by the two first…
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:…
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.”…
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 freePosted: Mon Nov 05, 2012 2:31 pm As announced at Directions US 2012, Microsoft recently released the Application Test Toolset for Microsoft Dynamics NAV…
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…
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: And this is the alternative flavor: Note that: the alternative is only used when the statement following the value set…
Read with me what the Microsoft Dynamics NAV 2009 Developer and IT Pro Documentation phrases on BEGIN/END, i.e. compound, statement: In some cases, the C/AL syntax only allows you to use a single statement. If however you have to execute more than one simple statement, the statements can be written…
In my previous post in this series I addressed the first sync with coding standards, i.e. removal of redundant record references. This post is about a small one, but nevertheless a sync with coding standards. Have a look at COD400 (see screen shot). It’s as simple as that. As the…
So in my chat with MS operations on insert rights for our add-on on NAV 2103 it became clear why we didn’t have these insert rights (yet) in our newly configured NAV 2013 development/demo license. Gary Winter’s comment however argues this and I truly hope he’s right, because using…
In C/AL we address fields and methods of record variables using the syntax <Record>.<Field> and <Record>.<Method>. To make coding somewhat simpler and the resulting code leaner, with the goal of being easier to read, C/SIDE – uhh NAV DE now we’re on NAV 2013 – has a couple of ways…