Related Posts
Anyone joining Deloitte India on 19th September
Community Builder
Did you get an increment during covid year?
Additional Posts in Salesforce Professionals
Bowl Leader
Hiring for a seasoned SFDC Admin located in Canada within an established group of Admins at Yelp. Additional job specs in the job posting below. Seeking someone with 4+ years of experience directly implementing on the platform for orgs of at least 500 users.
https://jobs.lever.co/yelp/28a6bc03-8304-42b3-ac95-8ee8099cdfe8
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.
🤨
Are you sure you need them to be a pkcklist? Seems like a really long picklist. Maybe have them as a prompt on a flow and use T/F to mark response. You also have lwc you can try building.
I was thinking flow too thank you
Custom object to store the pick list values then a lightning component (or maybe a flow) that replaces the field. The idea is, you'd query the custom object for the values to be displayed, the user selects the values they want, then drop them into a text field onto the record.
Thank you this could work!
Have you tried creating another field type as text area long or text area rich to have over 30,000 character entries?
You can also try storing these values in a custom metadata and then use a component to display in the pick lists on the record page. This gives you as an admin the ability to modify these values when needed (without the need to change code and deploy) + you can store the values on the record in a semicolon separated list, which can be parsed as the previous answer suggests.
Screen flow that maps the picklist values to a custom field that has those values
Thank you!!
Have the shortened identifying values show as picklist values, and then a matching custom field (with the full value) that is populated through a flow when the corresponding value is selected on the picklist.
How will they analyze the resulting data? Show them a report of mocked up data before you deploy to production. Reporting on multi select is so bad that we usually have to rework the solution in 6 months because they hate the report. Suggestions above are a start but also consider a proces to convert the text field back to a grid or boolean values for easier analysis.