Comment

Avatar

Level 4

22-11-2021

Hi Matt, this may expand on the topic somewhat, but our biggest issue isn't that the number of rows of detail is limited in the initial view (talking especially about a report in a dashboard), its that whatever you have built into the grouping header for the report (which is often the reason you built the report in the first place) -- be it an average, or a sum, or whatever it might be -- only takes into account the visible rows, not all the data for the report.


We have to explain and remind our users over and over that the initial values they see when the report displays are not meaningful until they See More or click on the report name. So they wait for the initial dashboard load, get results that don't represent what the report is for, and then have to take another step to load the full report and only then get good info.


Again, that may be specific to dashboards vs exactly what you're asking, but thought I'd throw that in there!