Picklist ID-Value pairs - Ideas - Salesforce Trailblazer Community
Trailblazer Community

All Ideas

Idea Details

Post an Idea
This idea has been delivered and can no longer be voted or commented on. If you’d like to add to this conversation, please post a new idea.
3,010  Points voting closed
Delivered in Spring 17
Delivered in Spring 17

Picklist ID-Value pairs

Customization & App Building

Typically, when building integrations to a system, you can key off an ID (typically an integer) that is associated with a displayed value.

When the ID is separate from the Display Value, this allows for the Display Value to be changed over and over, following the needs of a business unit, marketing team, usability consultant, etc.

The Display value can change and the behind-the-scenes integrations (both pushing data into the system and pulling data out of the system) never have to change, thereby seperating IT function from the business.

Unfortunately, Salesforce does not easily accomidate this standard and Picklist values are stored as text, both in the record itself as well underlying meta data. When building integrations, you have to key off the string and not the ID. Therefore, every time a business unit, marketing team, usability consultant or whoever decides the value in a picklist should be changed, ALL integrations that interact with that field need to be changed. If there is an upstream integration, where another system is pushing that data into Salesforce, that integration has to push the new string value. If there is a downstream integration that relies on data coming from Salesforce, that integration needs to handle the new string value.

Instead of being able to respond quickly to a change requested by a business unit, marketing team, usability consultant or whoever, that change requires significant involvement from IT.

This idea would be to expand the current functionality of the Picklist to include an associated internal ID.

· Flag

Latest Comment from Salesforce

  • Vladimir Gerasimov - 4 years ago

    This has been delivered as part of Spring '17 release.

    Please check out my blog post for more details about how this was implemented and how to benefit the most from using Picklist value API name functionality in your org.

    Thanks again for commenting and contributing to this idea!
  • Upvotes
  • Downvotes



from AppExchange


No results found.

Help us to keep IdeaExchange clean by pointing out overlapping ideas. We'll investigate your suggestion and merge the ideas if it makes sense.



Thanks for your merge suggestion. We will review it shortly and merge the ideas if applicable.

Salesforce takes abuse situations very seriously. Examples of abuse include but are not limited to posting of offensive language or fraudulent statements. To help us process your request as quickly as possible, please fill out the form below describing the situation. For privacy and security reasons, the final outcome of an abuse case may not be revealed to the person who reported it.


Thank you for your feedback. We take abuse seriously and will investigate this issue and take appropriate action.