Limit imported records to existing picklist values - 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.
1,790  Points voting closed
Delivered in Summer 16
Idea is generally available.

Limit imported records to existing picklist values

Operational Reporting

Carelessness and ignorance can reek havoc on data quality when people import all kinds of data into a field that expects defined picklist values. This is why sysadmins should be able to define per field, if imported data must match the defined picklist values or not. Example: we have a rather small (30+) list of industry picklist values, but my most recent report returned 561 (!) different industries.

· Flag

Latest Comment from Salesforce

  • A.A. Ron - 4 years ago

    Restricted picklists were in closed pilot in the Winter '16 release. In Spring '16 they move to open beta. This means that they will be available in all Developer Edition and Sandbox orgs, without requiring Salesforce to activate them, once Spring '16 is available everywhere. They are also available NOW in Spring '16 pre-release orgs. Get yours here:

    Also, be sure to join the "Global, Restricted Custom Picklists" Chatter group, where you will find a specification of the planned GA release, FAQs, and be able to collaborate with other members of the community:
  • Upvotes
  • Downvotes



from AppExchange

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.