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.
Learn more

From the blog

Off-topic: A C# lesson learned about conditional operators

If it was hard to write, it should be hard to understand, that’s an unwritten rule-that-rules-them-all of programming. You absolutely love to apply syntactical stunts to impress your coworkers, especially if you do C# and they don’t, don’t you? One of those stunts (at least from C/AL) perspective is a C-language type common feature known as conditional operator. It allows you to write this: 
a = b ? c : d;
when you would normally (in C/AL, for example) get more eloquent: 
if (b == true)
{
    a = c;
} else {
    a = d;
}
This (b == true) could have been replaced with just (b), but I put it there for clarity. But! (There is always a “but”!)

Capturing unhandled errors in JavaScript Control Add-ins

Not that I am saying it’s a good thing, but trial and error is a fairly common approach to debugging in the NAV world. We’ve all done it. Heck, even with the comprehensive testability framework built in, we all still do it more often than we’re happy to admit while sober. But the overlord of trial and error in NAV is development of control add-ins in JavaScript. JavaScript itself is making it difficult in the first place, and then integration with NAV makes it even harder. There is one situation in particular that’s adding a cherry on top of all of problems, and it’s the creepy “A script error has occurred” error message. It’s the equivalent of the BSoD.
Read all...