This article explains how to create and configure a custom picklist field on the Account object to maintain consistent county values. It also demonstrates how to use this picklist in Screen Flows and Record-Triggered Flows for streamlined data entry and automation.
It can be achieved by creating a custom picklist field on desired object to maintain and use the consistent values
Assumptions:
Steps to follow:
Create a new Custom field on Account Object
2. Select Picklist as Data Type
3. Enter the Field Label, select the option Enter values, with each value separated by a new line option and enter the Field Name as County. Click Next
4. Click on Next on rest of the step until we see the Save button and click on it to finish the field setup
Use Case 1: Display List of Counties in Screen Flow
b. Select Screen Flow
c. Add new Screen element or Open existing one > drag/drop Picklist to the Screen
d. Give any preferred Label. We will use County for our use case
e. Scroll-down in properties and select New Choice Resource in Choice
Note : Please ignore the component error as it will be resolved once Choice option is set
f. Click on Picklist Choice Set
g. Enter API Name, and select rest of the option as shown in screenshot below to configure Choice option
h. We should be able to see the fully configured Picklist with Counties. Click on Debug on top right corner to see it in action
Use case 2: Populate County on Account using Record-Triggered Flow
a. Open existing or create new Record-Triggered Flow using same navigation as shown in Step a of Use Case 1. Add Assignment element and configure as shown in the screenshot to populate the County
Note: We can either use Fast Field Update to populate or use Actions and Related Records option to update the assigned County on the Account
b. Save and Activate the Flow to see it in action
__________________________________________________________
Written by: Ruchit Patel | Forum Ambassador
Ruchit is an Application Architect with 12 x Salesforce Certified and has been working in the Salesforce ecosystem for more than 7.5 years. His core expertise lies in Apex, Lightning, and solution design, with a strong passion for tackling new challenges. He is an absolute learner who always strives for growth and believes in giving back to the Trailblazer Community by helping answer questions.
Submissions reflect only the opinions of the user who made available the Submission and not the opinions of Salesforce, regardless of whether the user is affiliated with Salesforce, and may contain or constitute products, services, information, data, content and other materials made available by or on behalf of third parties ("Third Party Materials). Salesforce neither controls nor endorses, nor is Salesforce responsible for, any Third Party Materials, including their accuracy, validity, timeliness, completeness, reliability, integrity, quality, legality, usefulness or safety, or any applicable intellectual property rights. Any Submissions made available through any message board or forum in response to posted questions, or that otherwise purports to answer any questions, including any questions about Salesforce or Programs, are made available for your general knowledge only and should never be relied upon as answers to your specific questions (even if an answer is marked as a “best” answer or with any similar qualifications). You should always contact Salesforce support for answers to your specific questions. Salesforce has no control over Submissions, and is not responsible for any use or misuse (including any distribution) by any third party of Submissions.
If you have questions, tap into the wisdom of our entire Trailblazer Community here: https://trailhead.salesforce.com/trailblazer-community/feed
005224343

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.