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.
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.
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('-').
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:
Even some standard NAV 2013 code has disappeared:
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.