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

Web Reference vs. Service Reference, Part 1

Once upon a time, Freddy has delivered a great series on connecting to NAV Web Services from a smorgasbord of technology flavors. If you are a .NET enthusiast, like me, the obvious choice is to connect through the tools that are at your disposal in Visual Studio: the proxy classes. A proxy class is a class which wraps a Web service functionality into a strongly-typed .NET object, and allows simpler communication through Web services. It hides away all intricacies of SOAP communication, authentication, serialization and deserialization, and exposes simple, easy-to-use objects. Every NAV Web service results in a series of proxy classes, and in Visual Studio the generation of those classes is as simple as clicking a mouse a couple of times.

Bug theater in Web services #5

Last Monday I’ve attended my second daughter’s birth, and then spent the week trying to relieve my wife as much as possible from anything but breastfeeding.

As a matter of fact, I’d like to keep doing it, it was not only a great break from daily worries, but also a fantastic occasion to spend all the time available with my closest and dearest, which I am not sure when I will have next.

It seems that there is life to keep going on, so I’ll now try to be back with my work and my blog.

Let me introduce bug #5: fields within a FixedLayout control.

Bug theater in Web services #4

In my country, there’s a saying: “A good horse has a hundred flaws; a bad one has only one.” It’s bad. People have asked me why I am doing this, and if I hate Web services because I’m blogging about their flaws. In fact, I love Web services, and as I said in the first post in this series – they are great. They are a good horse. A winner. The reason why I am doing this is because I want to share the problems I encountered over months of working with Web services intensively, as well as the solutions or workarounds I identified. Today, on the repertoire we have another security-related glitch, which has been confirmed to me by Microsoft, but as far as I know there has not yet been a hotfix for this. Bug #4: accessing Web services in multi-company scenarios.