Joined reports are powerful for multi-perspective views, but they come with notable limitations. The features that do not work in Joined reports: bucket fields, cross filters, report-level conditional highlighting, format switch-back, and certain chart and grouping behaviours.
What’s unsupported
| Feature | Why it’s unsupported in Joined |
|---|---|
| Bucket Fields | Bucketing is single-block-scoped; joined report doesn’t allow it |
| Cross Filters | ”Show records with / without” doesn’t apply across blocks |
| Conditional Highlighting at the report level | Per-block highlighting is supported, not whole-report |
| Switch format back | Once Joined, can’t be converted to Summary/Matrix/Tabular without rebuild |
| Time Series report features | Some advanced time-series settings aren’t supported |
| Standard Report Type “with” filtering | Some standard report types behave differently in Joined |
| Chart in some types | Funnel and certain combo charts have restrictions in Joined |
| Subscription with detail rows | Joined reports have specific subscription rules |
Bucket fields — biggest gap
In a Summary or Matrix report, bucket fields let admins categorise on the fly. In Joined, you have to fall back to:
- A formula field on the object — permanent, reusable
- Per-block filtering — split each tier into its own block (“Small deals”, “Medium deals”, “Large deals”)
- Pre-process the data with a Flow that stamps a category field
Cross filters — second-biggest gap
A cross filter answers “show Accounts that have at least one open Opportunity” — i.e. anti-join / inner-join logic on a related object. Joined reports can’t express cross filters, so you have to:
- Use a custom report type with “with” semantics for the same effect, then build the report as Summary or Matrix
- Use per-block filters that approximate the same thing
No going back
Once you flip a report into Joined format, the report-builder hides the format toggle. To “convert back” you’d rebuild the report from scratch as Tabular, Summary, or Matrix. Plan ahead — switch to Joined only when you’re sure you want multiple blocks.
Conditional highlighting
In Summary and Matrix, you can apply colour rules at the report level (red if Amount over 1M, etc.). In Joined, each block has its own conditional highlighting; you can’t have one rule span multiple blocks.
Charts
- One chart per joined report, pulling from a single block
- Funnel charts have limited compatibility in Joined
- Combo charts behave per block only
Other quirks
- Custom Summary Formulas across blocks are supported (cross-block formulas), but require careful syntax
- Detail Rows within a block work like standard; the “show details” toggle applies per block
- Group by Date with custom date groupings — per block, no shared date-grouping pivoter
When to choose Joined anyway
Despite limitations, Joined is the right answer when:
- You need a customer 360 view (Opps + Cases + Activities side by side)
- Comparing won vs lost vs open as separate blocks
- Multi-channel analysis (Email + Web + Phone cases each as a block)
For everything else, prefer Summary or Matrix and avoid the Joined trade-offs.
Common follow-ups
- Can I revert a Joined report back to Summary? — No, you’d have to rebuild.
- Bucket fields workaround? — Use a formula field on the object.
- Cross filter workaround? — Use a custom report type with “with” semantics.
Verified against: Salesforce Help — Joined Report Considerations. Last reviewed 2026-05-17 for Spring ‘26.