Hi Trailblazers,
I'm wondering how others handle user requests for many different custom picklists (and subsequent record types) for activities. We have several different sales teams - and each want their own customized picklist options - for logging tasks and events.
According to our Optimizer report, we're still within best practices for the number of record types we have, but we're cautioned for having too many custom profiles with a low number of users in each. I don't know of any workarounds. As I understand it - for each object (where we want a custom picklist) we need a separate record type and profile to assign it to.
I'm looking into reorganizing our role hierarchy and permission sets (moving to using permission set groups instead of custom profiles and individual permission sets). So, I'm looking to see if there's a better way to handle my custom picklist / custom profile issue. Any ideas (or validation of our current setup, lol) would be greatly appreciated.
@Jessica Higgason Picklist value's visibility are always based on record types, so I would recommend creating record types and assign them with corresponding picklist values. There is no other way ( unless you want to do some coding) to display picklist values based on a certain business rule.
Having said that, have you looked at using Dependent Picklists? You can split the existing picklists into sub-picklist fields and set up value dependencies. This will help when the user interacts with these picklists displaying a cleaner approach rather than having a long-list of values in a single field.
