---

Robust Auto-Numbering in Dynamics 365 for Sales

Because even numbers deserve structure.

---

There’s something oddly satisfying about a well-structured ID. Clean. Predictable. Sequential. But anyone who’s ever had to implement auto-numbering in Microsoft Dynamics 365 knows the struggle: duplicate numbers, skipped sequences, race conditions, and the all-too-familiar “Wait, why did it jump from 2027 to 2030?”

Yep. I’ve been there. In fact, I’ve lived there.

Today, I want to walk you through what’s possible in Dynamics 365 for Sales (as of version 9.0), why auto-numbering is such a pain for high-throughput environments, and how you can finally implement a robust solution—without losing sleep or data integrity.

---

The Built-In Numbering System: Great… Until It’s Not

---

Let’s start with the basics. Out of the box, Dynamics 365 already comes with auto-numbering fields for specific entities like:

• Contracts
• Cases
• Quotes
• Orders
• Invoices
• Campaigns
• Articles
• Categories
• Knowledge Base Articles

But here’s the kicker: Microsoft only allows minimal customization. You can change the prefix and define a 4–6 character random string, but that’s about it. And the incremental numeric section? Always fixed to 6 digits. Not exactly enterprise-flexible, right?

Want to change the step size? Nope.
Add a suffix with the fiscal year? Sorry.
Format it with leading zeros, region codes, or a smart pattern? You’re out of luck.

What sounds like a small limitation turns into a serious blocker for enterprise customers who rely on unique, readable, and structured numbering for auditing, reporting, or regulatory compliance.

---

Third-Party Tools to the Rescue (Almost)

---

For years, I relied heavily on tools like:

✅ Planet Technologies ID Generator
Simple, elegant, and smart. Supports prefixes, step sizes, zero padding, and even placeholders like year tokens. Find it here on Planet XRM.

✅ Celedon AutoNumber
A hidden gem. Similar to the Planet tool but with more conditional logic. You can even use dropdown fields to dynamically change the numbering logic (e.g., generate a different prefix for Partner vs. Customer vs. Lead). Bravo! Check them out here.

Both plugins do a great job… under the right conditions.

But there’s a problem they all share—race conditions. 😬
When you’re importing records or executing a workflow that spawns multiple entities simultaneously, there’s a real chance you’ll:

• Duplicate numbers
• Skip sequence entries
• Create broken dependencies

And suddenly, your supposedly unique IDs aren’t so unique anymore.

---

My Code-Free DIY Auto-Numbering Engine

---

Because necessity is the mother of reinvention innovation, I built my own Auto-Numbering logic using nothing but native Dynamics tools:

1. Custom Entity: A simple entity called NummernGenerator to track counters.
2. Calculated Fields: Concatenate year, prefix, and padded number into a final ID.
3. Workflow: On record creation, retrieve the current number, assign it, and increment the counter.

Bonus? I built a year-rollover feature so the generator resets in January or any custom month you want.

And all this without a single line of code. Just standard Dynamics + some clever logic.

Still, it’s not 100% race-condition-proof under heavy load, but it gets the job done for many common business scenarios.

---

The Game-Changer: Native Auto-Numbering for Any Entity (Dynamics 365 v9.0+)

---

Here’s where it gets interesting.

With version 9.0 of Dynamics 365, Microsoft quietly introduced native support for custom auto-numbering fields on any entity. Yes—you read that right.

It’s now possible to:

• Add auto-numbering to custom entities
• Mix elements like static prefixes, sequential numbers, random strings, and dates
• Format unique IDs like INV-2019-000123 or Q3-EU-0456-X

This is exactly what many of us have been waiting for. And yet… there’s a small caveat:

Microsoft forgot to expose it in the GUI.

That’s right. No way to set this up directly from the Dynamics UI. Which is where the trusty XRM Toolbox comes in.

---

The XRM Toolbox Plugin You Need

---

Thanks to the community, there’s now a plugin for XRM Toolbox that lets you:

• Define auto-numbering fields for any entity
• Edit existing system-managed fields (yes, even quotes and orders!)
• Apply advanced logic like conditional tokens, randomized values, and year-based sequencing

You can check it out in the XRM Toolbox plugin store. It’s saved me hours of work and a few grey hairs.

---

Summary: Your Auto-Numbering Checklist

---

So what’s the best solution for you? Here’s how I’d decide:

✅ Need fast deployment with some logic → Go with Planet or Celedon plugins
✅ Need flexibility without race conditions → My DIY approach is great for controlled scenarios
✅ Want native performance and zero-code scaling → Use the new v9.0 features + XRM Toolbox

And always, always test under realistic load. Because what works in dev might not survive production.

Stay clever. Stay responsible. Stay scalable.
Your Mr. Microsoft,
Uwe Zabel

---

🚀 Curious how enterprise-ready Dynamics 365 has become for real-world business scenarios?
Follow my journey on zabu.cloud—where cloud, AI, and business strategy converge.
Or ping me directly—because building the future works better as a team.