Great question—this is a common concern when migrating from flexible legacy systems to Business Central’s stricter data structures. Here's how you can frame it:
✅ Why the 20-Character Limit Exists
The No. field in Business Central is a primary key used across many tables. Extending it beyond 20 characters would impact performance, data integrity, and upgrades. Microsoft has intentionally designed it this way to keep the system stable and scalable.
🔄 Item References: Industry Best Practice
Many businesses with long legacy item numbers adopt Item References. It allows storing the full 30-character code without touching the core structure of BC. This model is widely used in industries like automotive, pharma, and electronics.
🧠 Key Messaging to the Client
“You’re not alone—many companies with long part numbers use Item References successfully.”
“Keeping the No. field short protects your system from technical debt and makes future upgrades smooth.”
“We’ve added a smart lookup so users can still use your 30-char code. The system will resolve it instantly.”
💡 Real-World Example (Condensed)
One of our clients in industrial components had 28-character part numbers. We:
Stored them in Item References
Created custom search and validations
Displayed the long code on all documents They quickly adapted and found the system easier to use in the long run.
🧩 On Manual Numbering
For manual number series, recommend a condensed format or structured shorthand (e.g., key attributes or product family codes) that retains recognition but fits within 20 characters.
🔚 Final Thoughts
Changing habits is hard, but the long-term benefits of compliance with standard BC design outweigh the short-term discomfort. Your solution with the smart search and custom layout is exactly the right approach.
✅ Mark this answer as verified if it helps you.
