From the Microsoft Dynamics NAV Blogs: Transaction Integrity; NAV 2013 Test Toolset; NAV 2013 Management Pack for System Center; Visual Production Scheduler

Transaction Integrity with Connected Systems: Recently Vjekoslav Babic wrote about this subject on his Navigate into Success blog.

"With .NET Interoperability around, it's very likely you'll be synchronously calling external web services from C/AL, to exchange data. I won't go into discussing whether or not this kind of architecture is good (my own position is that it isn't), you may end up having situations where your C/AL code simply makes a synchronous call to external systems, such as web services.

Any external call is an expected point of failure. An important question you must always have in mind when calling external functions is transaction integrity. When writing code that targets only NAV, the structure of code is largely irrelevant, as long as you are not using COMMITs (which is another thing you should avoid at all costs). However, as soon as you introduce external calls, the structure becomes critically relevant. Critically relevant."

Babic says the rule is: whenever you're making external calls from C/AL, make sure they are the last thing that's called in the transaction.

You can find out why here.

NAV 2013: Implementing the Application Test Toolset: On his blog, Waldo explains, that ever since NAV 2009, there's been some kind of framework built in the C/SIDE environment that can deal with application testing. Usually it's referred to as "Testing Framework" or "Test codeunits" or "Test Toolset" or "probably-some-kind-of-other-description-I-don't-think-of-at-this-moment-but-deals-with-testing-the-functionality-of-your-(customized)-NAV-solution," he says.

As his company is rebuilding its internal solution for NAV 2013, he says he has to include the Test ...