Comments for How to OMA!

Comment on Checking Where Used 100 Times Faster in OMA8.5 by Natalie

Natalie — Fri, 21 Sep 2012 06:48:44 +0000

Thanks for this blog entry - I updated my OMA from version 8.03 and did not discover any where-used performance improvements.
Unfortunately this important hint is not mentioned in the manual or changes document.

Comment on Bye Bye NAV Development Environment by Luc van Vugt

Luc van Vugt — Thu, 16 Aug 2012 12:46:48 +0000

RML

Comment on Aaargh! Where is that COMMIT? by Reijer Molenaar

Reijer Molenaar — Sat, 21 Jul 2012 13:03:25 +0000

Yes you’re right! That’s sometimes an easier way to do it. Then you don’t have to modify any object.

But there are COMMIT’s in disguise that are harder to find. After an “IF CODEUNIT.RUN” there is also a commit that you cannot find with the code coverage. The CONSISTENT(FALSE) command is bullet proof.

You can also use it when you are debugging and you want to rollback your transaction at the end.

Comment on Aaargh! Where is that COMMIT? by ara3n

ara3n — Sat, 21 Jul 2012 12:48:54 +0000

You can also use code coverage and then filter on commit and see where the commit is.

Comment on Stick to the Guidelines!! by Natalie

Natalie — Mon, 16 Jul 2012 06:35:01 +0000

Thanks for the feedback, Reijer!
Still wondering why Microsoft works against its own two-space-indent rule …

Comment on Bye Bye NAV Development Environment by Reijer Molenaar

Reijer Molenaar — Sat, 14 Jul 2012 12:25:46 +0000

Hmmmm, ok, I agree, it’s not for 100% certain.

But I think that the meaning of “until were able” means that they want to go there.

The sooner the better I say!

Comment on Bye Bye NAV Development Environment by Luc van Vugt

Luc van Vugt — Sat, 14 Jul 2012 10:03:50 +0000

Hi Reijer,

Carefully read the comment from MS on which you base this post.
What is said is (quoting only the sentence regarding the dev environment):

“… until we’re able to fully move the development environment to the RTC.”

So this does not say it will be.

b rg
Luc

Comment on Stick to the Guidelines!! by Reijer Molenaar

Reijer Molenaar — Sat, 14 Jul 2012 09:19:39 +0000

Natalie, I just got a confirmation that they made a mistake in the new document. The 3 space indent is the right way to do it. And Ralph, I also reported the wrong CASE statement so it will probably be corrected.

Comment on Stick to the Guidelines!! by Ralf Dübsch

Ralf Dübsch — Fri, 13 Jul 2012 18:44:23 +0000

It would be a big surprise to me if the mentioned document is really valid in this case. To me it doesn’t make any sense to start a new indentation “tradition” for IFs…
And something’s fishy on the website. You see it in section “Order in Expressions”. There the code in the YES CASE is badly indented.

Comment on Stick to the Guidelines!! by Reijer Molenaar

Reijer Molenaar — Fri, 13 Jul 2012 11:28:50 +0000

Yes indeed, it seems you’re right. This comes quite as a shock to me!!

However, I cannot find this 2 indent a single time in the new NAV2013 database. You would almost say that someone made a mistake when he wrote this new guideline document…

I will ask Microsoft what’s the right way to break an if statement.