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
AL Object ID Ninja v3.0 Platform Launching on December 15
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.
The response was overwhelming — a clear, resounding “Yes, please!” from the market.
To everyone who signed up: thank you. Truly. Your trust is the single biggest motivator behind the speed and intensity of development happening right now.
I even extended the early-bird window by two extra days to accommodate the late rush, but now the big lifetime discounts are officially closed and I'm no longer collecting “count-on-me” registrations.
That said, if you feel you should still receive a discount, reach out to me directly before December 22, and I’ll gladly provide a 15% voucher. No justification needed — just ask.
A Story About Trust: Why LS Retail Moved from Private Endpoints to the Hosted Ninja Backend
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. LS Retail has been using AL Object ID Ninja literally since day one—the very day it was released. Not only that: they never used the public backend. From the beginning, they chose to run Ninja entirely on their own infrastructure.