AL Object ID Ninja

Zero-configuration, dead-simple, lightning fast, no-collision object ID assignment for multi-user repositories

No collisions, ever: Real-time, conflict-free ID assignment that always gives every developer a guaranteed unique object ID.
Lightning-fast: Get your conflict-free object IDs instantly, with IntelliSense integration.
Zero-configuration: No setup, no onboarding, no settings — you work exactly like before, and it silently keeps your IDs clean.

From the blog

Retiring NavigateIntoSuccess.com

A couple of months ago, when I asked my friends on Facebook and Twitter if anybody knows how to move a WordPress blog to another domain, everybody said that I was crazy. You don’t do these things, they said. And yet, when they heard the reason why I was about to leave my old domain, everybody agreed.

NavigateIntoSucess.com has served me well. I moved my public WordPress website to this custom domain very early on. It has become a kind of a brand. But it is a pretty long name. You can easily mistype it. It’s difficult to remember it if you only occasionally stumble upon it. It doesn’t at all relate to me as a living person behind it. So I decided to move it all to a fresh new domain: vjeko.com.

How Do I… Videos on MSDN

MSDN has started running a series of the How do I… videos for Microsoft Dynamics NAV 2013 (feed here). The idea is to showcase a technical feature in 5-15 minutes. The project is still ongoing, but a number of videos have just been released and announced on the Microsoft Dynamics NAV Team Blog.

The project is a joint effort by Plataan and Microsoft, and I participated as a technical expert in charge of seven videos. I’ve already recorded five of them, out of which three are online.

You can find the links below, and please come back to this page as I’ll update it as more videos are published.

Transaction Integrity with Connected Systems

Broken pencil 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.

I’ve talked about this during my 2012 NAV TechDays session, and I promised I’d blog about it – so, here it goes.