Spring ’23 Release Highlights: Picklist Improvements (and a “Heads Up!”)

Thursday, January 12, 2023

As we continue our countdown to the Salesforce Spring ’23 release, we’re once again peppering the lead-up to launch with our picks for the most exciting updates, upgrades, and improvements heading to orgs everywhere! That’s right, it’s another round of Release Highlights — and this time we’re taking a look at some changes to Picklists that will have admins cheering (and one that might be a bit of a headache if you’ve been avoiding best practices).

Let’s dive in!

Bulk Manage Picklist Values

First up is a real potential time saver, the ability to delete, activate, deactivate, or replace multiple custom picklist field values at once. Previously, you modified them one at a time (and that means lots of scrolling, scanning, clicking, saving, and repeating). For internal admins, this’ll mean easier configuration and customization, shorter turnaround on org projects and less institutional inertia to overcome when deciding how much effort it’ll take to make meaningful improvements!

And, for those with partners or firms doing the admin work in Salesforce, that’ll mean a reduction in invoiced hours to accomplish those goals. So a time savings or a $$$ savings, or both depending on how hands-on your Salesforce staff is!

This was previously a Beta feature, but it’s going wide with the release (aka, “Generally Available”) and to access it, all you have to do is:

Go to the custom field definition page for the picklist field.

In the Values and Inactive Values sections, there’s a checkbox next to each picklist value.

You can select multiple values and use one of the new buttons: Delete Selected, Deactivate Selected, Replace Selected, or Activate Selected.

And you’ll be saving time in no time!

Clean Up Inactive Picklist Values

This is another (former) Beta feature, going to general availability in Spring ’23 — the ability to bulk delete inactive unused picklist values, manage inactive picklist values, and enforce limits on inactive values for custom picklists (the goal being to make it easier for admins to improve system performance and overall health). Not to mention save their sanity and clicks, by turning all those one-off efforts into a more manageable bulk process!

All admins willl need to do is:

Head to the Inactive Values section of the picklist field, and click Delete Unused Values.

After you delete unused values, if a picklist is unbound and the total number of inactive values falls below the limit, the picklist is set to bound!

Easy peasy.

Heads Up! Inactive Picklist Values are Getting a Limit

Last, but not least, less of an exciting feature and more of a wake-up call to admins who might’ve been a little cavalier about cleaning up those inactive picklist values. Announced in Spring ’23, and enforced in Summer ’23, we’re losing the ability to have unlimited inactive picklist values.

And sure, every admin’s going to agree that having infinite inactive picklist values is unnecessary, and out of line in terms of best-practices — but I’d still bet there’s an org somewhere that’s reading this news with some sweat forming on their brow.

For now, we’ll see a toggle in the picklist settings that allows us to remove the upper limit on the number of inactive values:

…but starting in Summer ’23 that option will disappear and we’ll all be limited to 4,000 such values.

So, if that’s going to affect your org, now’s the time to start cracking down and cleaning up! (And I’ll bet you’re really glad about that newfound ability to mass cleanup those inactive values we mentioned earlier).

Tomorrow’s the very first day org’s will start seeing Spring ’23 (but for most of us, we’re still a couple weeks away) so, as always, stay tuned here for more Release Highlights as well as your standard Salesforce news, tips, and tricks — and feel free to drop your favorite Spring ’23 features in the comments!

Until next time, keep working hard, smart, and happy. And we’ll see you in the cloud!

Chris Stegall
Chris Stegall
Marketing Director @ MK Partners.