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.

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…