Plan requirement
| Subscription | Suite Professional or higher, Explore Professional or higher |
| Access | Admin |
The limits that shape what you can build: how many reports on a dashboard, how far back data goes, how large an export can be.
Where the limits sit
- Reports per dashboard, and per tab.
- Rows returned by a single report.
- Export size, beyond which an export is split or refused.
- Scheduled deliveries, how many and how often.
- History, how far back the data goes.
The exact figures depend on your plan and are shown in Explore itself.
The one that bites first
Rows per report. A report grouped by ticket, or by individual customer, hits it quickly and silently truncates, which looks like a number that has stopped growing.
Group by something with fewer values, or filter harder.
Dashboard limits are a design hint
Long before you reach the limit, a dashboard with twenty reports has stopped being read. Tabs help, and splitting into two dashboards for two audiences usually helps more.
Slow is a signal, not a limit
A report taking a long time is usually reading more than it needs: too wide a date range, no filters, grouped by something with thousands of values. Narrowing it is both faster and more readable.
Exports are not a data warehouse
Where somebody wants the full history in a spreadsheet every week, the answer is usually a proper export route or a scheduled dashboard, not repeatedly pushing against the export limit.
Check before you promise
If somebody asks for reporting over several years at ticket level, confirm the history and row limits before committing. That conversation is much easier in advance.
Comments
0 comments
Article is closed for comments.