AL Object ID Ninja

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.