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: An Apology, a Decision, and a Month on the House
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.
AL Object ID Ninja MCP Server Is Here
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.
When GUIDs Collide: The App ID Problem Nobody Expected
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.
And yet, here we are. Talking about duplicate App IDs in Business Central.
- 1
- 2
- 3
- 4
- …
- 160
- Go to the next page
