If you have been part of the Salesforce ecosystem for a while, you’ve likely seen this specific Idea on the Salesforce IdeaExchange at some point. For over a decade, the request to increase the standard Name field length from 80 to 255 characters has been one of the most-voted and highly discussed topics in our community.

We finally have a definitive answer from Salesforce, and while it might not be the news many were hoping for, it brings much-needed clarity.

The Update

Salesforce has officially closed this idea. After conducting a deep technical review, the platform team concluded that increasing the field length is not feasible.

It’s easy to look at a field length limit and think, “How hard can it be to just change a number in the database?” However, as Salesforce explained, this isn’t a simple configuration change. The Name field is baked into the foundational infrastructure shared by every custom object, in every org, across the entire platform.

Expanding this field would require a massive, platform-wide data migration. Given the immense risk of disruption to existing data and the complexity involved, Salesforce has determined that this change cannot be made responsibly. They’ve chosen to prioritize platform stability over this specific enhancement.

Why This Matters (And Why We Respect the Decision)

While this is disappointing, there is a silver lining in how Salesforce handled it. For years, this idea sat as a “placeholder.” By choosing to close it, they are being transparent about what is technically possible versus what is a platform-wide risk. As admins and developers, we value stability above almost anything else—and a change that could potentially corrupt data across the entire ecosystem is something we all want to avoid.

So, What Now?

If you are currently hitting that 80-character wall and need more space, you aren’t completely out of luck. Salesforce has provided a supported workaround for those who need to store longer names.

The Strategy:

1. Switch to Auto-Number: Convert your standard Name field to an Auto-Number format.
2. Use a Custom Text Field: Create a new custom text field (up to 255 characters) to store your full name value.

A Note of Caution: Before you jump into this, please keep in mind that this workaround does change how your objects behave—specifically regarding lookups and search functionality.

Pro-tip: Don’t do this in production! Spin up a sandbox, map out your existing integrations, test how your search views look, and ensure your reports don’t break.

Let’s Keep the Conversation Going

It’s never fun to see a highly-requested feature get shelved, but having a clear answer allows us to stop waiting and start building differently.