A Bucket Field is an inline categorisation you create directly inside the Report Builder, without changing the underlying data. It maps existing field values into named buckets — useful when the underlying picklist or text field has too many values, or when you want to group values differently than the source data does.
Example: Industry has 50+ values (Manufacturing, Aerospace, Automotive, Electronics, Software, Healthcare, Pharma, Hospitality, Tourism, Retail, etc.). You bucket them into 5 categories — Manufacturing, Tech, Healthcare, Retail/Hospitality, Other — for an executive dashboard. The report displays the bucketed value; the underlying record's Industry field is unchanged.
Bucket types:
- Picklist Bucket — group picklist values.
- Text Bucket — group text values.
- Numeric Bucket — group numeric ranges (e.g., Annual Revenue: <$1M, $1-10M, $10-100M, $100M+).
Limitations:
- Per-report only — buckets exist inside one report. To use the same grouping in many reports, you have to recreate it (or build a formula field on the object instead, which is permanent).
- Doesn't update if values change — if the source field gets a new picklist value (e.g., "Cleantech" added to Industry), it won't auto-bucket; it falls into the "Other" bucket until you edit the report.
- Not filterable as a separate column — you can group by a bucket field but you can't easily filter on it across other reports.
When to choose a bucket vs a formula:
- Bucket: ad-hoc, one-off, exploratory. Quick analysis without changing the schema.
- Formula field: when the same grouping is needed in many reports, in record pages, in flows, or in validations. Add
Industry_Group__cas a formula on Account and use it everywhere.
Buckets are an elegant analyst tool — quick segmentation without engineering overhead — but for org-wide consistent grouping, a formula field wins.