AL Object ID Ninja

AL Object ID Ninja is now available as a GitHub Action and an Azure DevOps Pipeline Task. It scans your AL repository during CI/CD and fails the build if it finds any object IDs, field IDs, or enum value IDs that aren’t tracked by the Ninja backend.

I’ve been busy over weekend with completing a few work items that were in the cooking for a while. Some have been on my wish-list since day one, some have been brewing since a few years ago. It’s unbelievable how far certain architectural decisions can go, and I am genuinely excited to bring this new version to the daylight: 3.2.1.

I owe you an explanation. Not a corporate statement. Not a carefully worded legal notice. An actual explanation, from me to you, because you’ve trusted this tool – and by extension, me – for years. You deserve more than a changelog entry. So here it is. Four years. My pocket.

So you’ve jumped on the agentic coding train. You’re using Cursor, or Claude Code, or Windsurf, or whatever the cool kids are using this week. Your AI assistant writes AL code for you, and life is good. Except… who’s making sure your object IDs don’t collide? Nobody, that’s who. Until now.

You know what’s supposed to be unique? Snowflakes. Fingerprints. And GUIDs. A GUID (Globally Unique Identifier) is mathematically designed to be so astronomically unique that if you generated one hundred billion GUIDs per second, you’d still have a better chances of being struck by lightning twice and then winning the lottery, all on the same day, than generating a duplicate.

I’ve just released Ninja 3.1.0 , and it adds something I’ve wanted for a while: language-model tool-based object ID assignment . In practice, this means that when an agent is writing AL code inside VS Code, it can now use Ninja directly as a tool to allocate and commit object IDs. No typing.

This past weekend marked an important milestone for AL Object ID Ninja. Backend version 3 is now live , running in production on: brand-new endpoints, the latest supported Node runtime, and fully covered by more than 1,300 automated tests . So far, it’s been running smoothly and reliably , exactly as intended.

This post is for teams running AL Object ID Ninja on their own backend . If you are using the hosted Ninja backend, you don’t need to do anything — the transition will be handled for you invisibly. What’s New I’ve published a new v3 version of the Ninja backend to the repository: 👉…

When I opened the early-bird sign-up page for AL Object ID Ninja, my goal was simple: to understand whether there was enough real interest in a fully supported, commercial-grade Ninja platform for me to commit myself to building it the way it deserves to be built. That question didn’t stay unanswered for long.

Every now and then a real story captures the essence of what a product is meant to do. This one did that for me. A few days ago, LS Retail, a long-time Ninja user, reached out and asked a simple question: “Can you help us move from our private endpoints to your hosted backend?” At first, this surprised me.

Fun fact from the past three months of AL Object ID Ninja: Ninja has handed out object IDs to 9,365 apps . Out of those, 297 apps were configured to use private endpoints. But here’s the interesting part: Only 122 apps were consistently configured correctly for all team members — meaning every team…

Over the past four years, AL Object ID Ninja has quietly kept thousands of teams out of conflict trouble. To plan the next chapter responsibly, I need a simple signal from you. What I’m asking If you intend to keep using the hosted Ninja backend after 1 January 2026 , please register your interest here: 👉 alid.ninja This is not a subscription.

EDIT: Click here to let me know if you intend to stay with Ninja premium backend and lock in your lifetime 35% discount. I hoped I would never have to write this post. When I first released AL Object ID Ninja back in September 2021 , my dream was simple — to give every Business Central developer a painless way to manage object IDs, forever free.

Long time no see, eh? 😳 I won’t offer no excuses, but I have been plenty busy with things that you’ll benefit in some way or another, far more than you’d benefit from me writing here. So, let’s jump straight into it. First things first. I just can’t express my gratitude to all of you who use it every day.

For all of you using AL Object ID Ninja, please read this post. There will be scheduled maintenance of AL Object ID Ninja back end on October 9, 2021, at 19:00 CET (UTC +2). The expected downtime is 30 minutes. During the maintenance, you will not be able to use AL Object ID Ninja to assign object IDs.

If you are using AL Object ID Ninja already then you may want to read this post. If not, then first install AL Object ID Ninja, then read this post 😀 Since its launch three weeks ago, this extension has exploded far beyond my expectations.

First things first. Yesterday evening, I’ve released AL Object ID Ninja v1.2.0 and there is really nothing new that you’d care about, functionally speaking. Check the changelog if you will , but trust me, you won’t be really blown away. But yes, unfortunately, it did merit a full minor version rather than just a patch number increase.

I have just released version 1.1.0 of AL Object ID Ninja . Here’s what’s new. Merge synchronization In previous versions, you could only synchronize full information. This type of synchronization simply recorded in the back end whatever it finds in the front end.

If it does what the documentation says it does, I can only say: “Build this man a statue!” Awesome job. — Waldemar Brakowski (@wbrakowski365) September 11, 2021 One of the biggest obstacles to AL team development (is there any other kind?) is object IDs. IDs are supposed to be easy: just pick the next free one and off you go.