Picklist versus related object
Key Takeaway
Use a picklist for a consistent set of values in one field. Use a related object when the thing being chosen needs its own data and should appear as related records on the other object.
When a field needs to hold a choice, an app builder can store it as a picklist or as a relationship field. A picklist is a list of values defined on the field, so it keeps values consistent inside one field. A relationship field points to a record in another object. With a related object, each choice is a full record with its own fields, linked to other records across objects.
Choosing a picklist or a related object
If the goal is a consistent set of values in one field...
Choose a picklist, for example for a customer status or a product flavor.
If the thing being chosen needs its own data and should appear as related records on the other object...
Choose a related object. For example, contacts appear as related records on an account.
The two options also differ in how they store a choice and who maintains the list.
| Picklist | Related object | |
|---|---|---|
| What the field does | Stores a value from a list | Links the record to a record in another object |
| What one choice is | One entry in a value set (the picklist's list of choices) | A full record in an object with its own fields and records |
| Maintaining the list | Picklist values are managed in Setup | Records are added like any other record, for example by clicking "New" in the Related tab of the parent record |