What’s better: boolean or picklist?
Summary
In Salesforce, choosing between a boolean field and a picklist to track binary responses can significantly impact data clarity and flexibility. While booleans only capture true/false values, picklists offer a blank default for unanswered questions and more descriptive options like "Yes, but trying to quit." This approach enhances data quality and allows easy future modifications without complex changes. Salesforce teams should consider picklists over booleans when tracking nuanced or incomplete responses.
Takeaways
- Use picklists to track unanswered or nuanced responses beyond true/false.
- Booleans only capture positive or negative answers without a null state.
- Picklists allow adding new response options without schema changes.
- Choose meaningful picklist values like Yes/No over True/False for clarity.
- Consider data quality implications before defaulting to boolean fields.
When tracking a positive and negative response in Salesforce, most consultants would simply create a boolean field and call it a day. But you’re a “good enough” consultant, so you know there’s another choice. The other option is a picklist with “True”/”False” or “Yes”/”No” choices. Here are the differences between these approaches. Imagine a field that records whether a contact smokes or not. Firstly, with a boolean, the answers can only be positive or negative. It’s impossible to know whether the question was even asked. With a picklist, the default is blank. This means the question hasn’t even been answered. Choosing “No” confirms the response and that it was negative. Secondly, sometimes “Yes” or “No” answers make more sense than “True” or “False”. There’s a nuance that can be leveraged. Lastly, a picklist allows for easier modifications. A new answer, “Yes, but is trying to quit” can be easily added to a picklist, but not a boolean.