Blog Post List

  • Some Compounds Statements

    Luc van Vugt

    Have a look at these code samples and tell me where a compound statement, i.e. BEGIN-END, should be constructed to get the code work right.

    Just dare without going into NAV and verify. Geeked

    Sample 1

    1. SalesCommentLine.SETRANGE("Document Type",SalesQHeader."Document Type");
    2. SalesCommentLine.SETRANGE("No.",SalesQHeader."No.");
    3. WHILE SalesCommentLine.FIND('-') DO
    4.   SalesCommentLine.DELETE;
    5.   SalesCommentLine."Document Type" := SalesOrderHeader."Document Type";
    6.   SalesCommentLine."No." := SalesOrderHeader."No.";
    7.   SalesCommentLine.INSERT;

    Sample 2

    1. IF AccountingPer2.FIND('>') THEN
    2.   FiscalYearEndDate := CALCDATE('<-1D>',AccountingPer2."Starting Date");
    3.   AccountingPer3 := AccountingPer2;
    4.   AccountingPer2.SETRANGE("New Fiscal Year");
    5.   AccountingPer2.FIND('<')
    6. ELSE
    7.   ERROR(Text001);

    Sample 3

    1.  CASE "Action Taken" OF
    2.    "Action Taken"::Won:
    3.      IF Opp.GET("Opportunity No.") THEN
    4.        SalesQuoteEnable := Opp."Sales Document No." <> '';
    5.    "Action Taken"::Lost:
    6.      CalcdCurrentValueLCYEnable := FALSE;
    7.      SalesQuoteEnable := FALSE;
    8.  END;

    Sample 4

    1.  CASE LOWERCASE("XBRL Item Type") OF
    2.   'stringitemtype','string':
    3.     "Source Type" := "Source Type"::Description;
    4.   'monetaryitemtype':
    5.     "Source Type" := "Source Type"::"General Ledger";
    6.   'decimalitemtype':
    7.     "Source Type" := "Source Type"::Constant;
    8.  'sharesitemtype' :
    9.     "Source Type" := "Source Type"::Constant;
    10.  'uriitemtype':
    11.     "Source Type" := "Source Type"::Description;
    12.   'tupletype':
    13.     "Source Type" := "Source Type"::Tuple;
    14.   ELSE
    15.     "Source Type" := "Source Type"::"Not Applicable";
    16.     IF "XBRL Item Type" <> '' THEN
    17.       Description := STRSUBSTNO(Text007,"XBRL Item Type");
    18. END;

    Sample 5

    1.  WITH ResJnlLine2 DO
    2.    IF "Resource No." <> '' THEN
    3.      IF ResJnlTemplate.Recurring THEN BEGIN
    4.        TESTFIELD("Recurring Method");
    5.        TESTFIELD("Recurring Frequency");
    6.        IF "Recurring Method" = "Recurring Method"::Variable THEN
    7.          TESTFIELD(Quantity);
    8.      END ELSE BEGIN
    9.        TESTFIELD("Recurring Method",0);
    10.       TESTFIELD("Recurring Frequency","0DF");
    11.     END;

    For reference I have added numbers to each code line. Please use it as follows: if in case in Sample 2 the BEGIN should be added to line 2 and it's balancing END to line 4, you could suffice with writing Sample 2 - line2/line4.

    • 2013-7-30

  • NAV 2013 SEPA Credit Transfer and Direct Debit Updates - Netherlands - Arghhhhh

    Luc van Vugt

    Yesterday Microsoft Dynamics NAV 2013 SEPA Credit Transfer and Direct Debit Updates - Netherlands was released on PartnerSource. Something various partners and customers have been waiting for in The Netherlands. We too. But then for NAV 2009 R2. Instead of asking MS - and probably getting an unclear answer - I started my own investigation on the code to see if this would be an easy job to do. To my amazement I even didn't get to gathering relevant data to draw my conclusions from as I stumbled over code differences I was sure that wouldn't work. I even doubted if they would compile, however, they did. Let's have a look at PAG11000002.

    Ever seen this statement?

    IF "Detail line2".FIND('%1') THEN BEGIN

    Used to be a simple FIND('-').

    Or:

    IF Custm."Our Account No." <> '<>' THEN

    which used to be <> ''

    And this statement seems to have absorbed one of the NL local functionality code markers NL0002:

    Detail line2".SETFILTER(Status,' NL0002',"Detail line".Status::Proposal);

    ' NL0002', which IMHO should have stayed '%1'.

    Most objects seem OK, but those that do have some NL local functionality code markers, that normally is cleaned before release have similar issue:

    • TAB18
    • TAB23
    • TAB11000000

    Even some standard NAV 2013 code has disappeared:

    • TAB18
    • TAB23
    • TAB270

    Note that next to that, like before, captions have changed or aren't even provided (TAB11000005) or wrong (TAB311).

    Well, I just wanted to let you know and that I am trying to chase the right persons at MS to get this fixed.

    • 2013-7-2
Copyright 1995-2018 Dynamics User Group, all rights reserved.