Row limits and paging
Every visual on a DataPrism report loads a bounded number of rows, and the way it loads them depends on its type and on the fields you put on it. This page covers what a visual loads while you read a report: when it shows one page at a time, when it keeps a growing window instead, and how long the view settings you change stay with you. For setting the sizes an author saves, see Chart limits.
How each visual loads its rows
An author sets the size per visual under General > Limits; the defaults and maxima are:
| Visual | How it loads | Default | Maximum |
|---|
| Bar, Combo | One page at a time | 20 | 1,000 |
| Line | One page at a time | 100 | 5,000 |
| Bar, Combo, Line with a Legend field | One window at a time | 20,000 | 100,000 |
| Pie, Donut | One page at a time | 50 | 500 |
| Table | One page at a time | 50 | 1,000 |
| Matrix with Rows or Columns filled | One window at a time | 20,000 | 100,000 |
| Funnel | Its stages | 30 | 250 |
| Slicer, Slicer group | Values, one page at a time | 1,000 | 10,000 |
| Custom visual | A fixed number of rows | 1,000, or the row limit the visual declares | 100,000 |
| Map | One capped load | 50,000 points, or 10,000 shapes | 100,000 points, or 25,000 shapes |
- A page is a slice of the result: the footer counts where you are, such as 2/8, and Previous page and Next page move between slices. The Limit pick beside them sets how many rows one page holds.
- A window is a chunk the tile keeps and adds to. It offers Load more, with progress such as Loaded 20,000 of 85,000 rows, and when it can load no more, Row limit reached replaces the button.
- An Export, from the tile or the report, carries the whole result, not only the rows the tile has loaded; see Export reports and data.
- KPI and Cards show one value or a card per measure, so they carry no limit rows and no pager.
Pages or a window: what decides
- A Legend field on a Bar, Combo or Line chart splits each row into its own series, so a page of rows would not be a page of categories. The chart stops paging and keeps a window instead; take the field out of Legend and the page controls return.
- A Pie or Donut keeps its pages with a Legend field: it takes its grain from the legend and still slices the result page by page.
- A Matrix keeps a window while Rows or Columns hold a field; see Matrix.
- A legend-split chart that has loaded more than 2,000 rows shows a warning marker among its controls. Its tooltip reads A legend field splits each row into its own series, so this visual loads in server windows instead of pages - add a filter to narrow it.
- A Top N rule replaces the page size with the number the rule keeps, and the type's maximum still applies; on a chart that loads in windows the rule narrows the values and the window stays. See Top N.
- A Map takes one capped load, and that cap never combines with paging or a comparison. See Map visual.
The Limit pick, and whose value applies
- The Limit pick offers the sizes its type lists, such as 5, 10, 20, 30, 40, 80 and 100 on a bar chart, plus the chart's own saved size. Nothing above the type's maximum appears.
- While you read a report, your pick applies to your view and is kept in this browser only. While you edit the report, the pick writes the chart's saved size instead, so everyone opens the report at it; choosing the default size clears a saved change rather than storing it.
Your own settings, and how long they last
- A page size you pick, a sort you set, the search toggle and the column widths you drag stay in this browser for about 30 days after your last change to that chart.
- A drill position you leave a chart in, the expanded path of a Key tree, and the filter funnels you apply on a table or matrix header stay for about five days after your last change.
- A stored sort whose field has left the visual is set aside, so a stale choice cannot stop the tile from running.
- Reset in the report footer, whose tooltip reads Reset to the author's saved view, drops all of it at once and restores the saved view; it touches this report only, so other reports keep their own settings. See Read a report.
Questions, answered
Why did the page controls disappear when I added a Legend field?
A legend field pivots the result: each row becomes its own series, so a page of rows is no longer a page of categories. The chart switches from pages to a growing window with Load more. Remove the field from Legend and the page controls return. Pie and Donut are the exception: they keep paging with a legend.
Why is there a warning marker on a chart that has loaded a lot of rows?
On a legend-split chart past 2,000 loaded rows, the tile shows a warning marker among its controls. Its tooltip explains that the legend field splits each row into its own series, so the visual loads in server windows instead of pages, and that a filter narrows it. Filter the legend field to load less.
Why is there no pager on my chart?
The paging footer appears once the result has more rows than the type's default page size, or already spans more than one page; a small result shows no footer. A chart that loads in windows has no pages at all, and a KPI or Cards tile carries no pager either.
Does my page size pick change the report for everyone?
While you read a report, no: your pick changes only your view and stays in this browser. While you edit, the pick does change the report: it writes the chart's saved size, the same value General > Limits holds, and choosing the default size clears a saved change. For which value printed, exported and emailed copies use, see Chart limits.
Why did my sort and page size disappear after a while?
They are kept in this browser for about 30 days after your last change to that chart; a drill, a Key tree path or a header filter funnel clears sooner, after about five days. When an entry ages out, the chart opens at the saved view again. Reset clears everything at once, and none of it affects other people.
Does a custom visual follow its own row limit or the one I set?
A custom visual can declare a row limit of its own; Rows under General > Limits overrides it. Without either, the tile asks for 1,000 rows, and no value goes above 100,000. See Custom visual options, data and limits.
Why has a windowed chart loaded more rows than its window number?
A window asks for a number of rows, but rows that tie at its boundary travel together, so a load can land a little above the number. The count under Load more, such as Loaded 20,140 of 85,000 rows, shows what is really loaded.
What sizes does the Limit pick offer?
The sizes its type lists, plus the chart's own saved size, so an unusual saved value stays reachable; nothing above the type's maximum appears. A bar chart, for example, offers 5, 10, 20, 30, 40, 80 and 100.