Dynamically Sized Tables: Export a Whole Table as an Image
Introduction
A table widget on a dashboard normally renders inside a fixed frame. If the table returns more rows than the frame is tall, you scroll inside the widget to see the rest — which is fine on screen, but a problem the moment you export the dashboard as an image. An image export captures what the widget displays, so the rows below the fold and the columns off to the side simply are not in the picture.
Here is a table set to the fixed Large size. It returned 25 rows, but only 16 of them fit — the rest are behind a scrollbar, and an image export of this dashboard would stop at the same place:
Dynamically sized is a size option for table widgets that solves this. Instead of picking a frame and hoping the data fits, the widget measures its own results and grows to fit them: every row it returns is rendered, and every column you have chosen is visible. Nothing is hidden behind a scrollbar, so nothing is missing from the export.
Before You Begin
It applies to configurable tables only. That is the agents table, the tickets table, the organizations table, the queues table and the rest of the Configurable Table family. Charts, quick stats and scorecards keep the standard Small / Medium / Large sizes, and the option will not appear for them.
You need edit access to the dashboard holding the widget.
If you have not changed a widget's size before, see How to Change Chart Sizes.
Step 1: Open the Widget's Settings
Open the dashboard and click Edit. Hover the table widget you want to change and click its edit icon to open the widget settings.
Step 2: Set Chart Size to "Dynamically sized"
In the Selected Widget panel on the right, open the Chart Size dropdown. Alongside Small, Medium and Large you will find Dynamically sized:
Choose it and save the widget.
Step 3: Check the Result
Back on the dashboard, the same table now renders in full — all 25 rows, no scrollbar. Notice that the widget also became narrower: a dynamically sized table takes exactly the width its visible columns need rather than filling the row.
The widget will often look oversized in the browser — taller than your screen, so you scroll the page past it. That is expected. You are configuring this table to be exported, not browsed.
Exporting the Table
Export the dashboard image exactly as you normally would. Because the widget already displays every row and column, the image contains the complete table — there is no separate "export everything" setting to remember.
This works for scheduled exports too, so a weekly report that goes out by email arrives with the full table in it rather than the first screenful.
Getting the Most Out of It
Set your column widths first. A dynamically sized table honours the widths you have saved, so widen a column that holds long names and the export will keep that width. Because rows are a fixed height, text that does not fit is shortened with an ellipsis rather than wrapping onto a second line — widening the column is how you show it in full.
Drop the rows you do not need. Under Table Filters you will find Exclude rows with all 0's and Exclude rows with no data. On a dynamically sized table these are applied before the widget is measured, so filtered-out rows do not take up space in the export. On a table full of quiet organizations or inactive agents this can halve the height of the image.
Use the row limit. Most configurable tables have a "number of results" setting. Lowering it is the simplest way to keep an export to a sensible size.
There is no drag handle. The corner resize grip disappears on a dynamically sized widget, because the widget is now sizing itself. Switch back to Small, Medium or Large if you want to size it by hand again.
The Limits: Very Large Tables Still Get Cut Off
Dynamic sizing is not unlimited, and it is worth knowing where the ceiling is before you build a report around it.
Height: about 120 rows. The widget grows to roughly 5,000 pixels tall and then stops. Past that point the table starts scrolling inside the widget again — which means an image export of a 300-row table will still be cut off, just much further down than before.
Width: very wide tables also stop growing, at around 90 columns at the default column width (fewer if you have widened them). In practice almost no table reaches this, but a table that does will scroll sideways in the same way.
If your table is past the row limit, you have three good options:
Filter it down. Turn on Exclude rows with all 0's — rows with nothing in them were not telling you anything, and dropping them often brings a table back under the limit on its own.
Split it up. Several dynamically sized tables, each filtered to one group, brand or site, will each export in full. A handful of complete images usually beats one truncated one.
Use a CSV export instead. For a genuinely large data set — hundreds of rows you intend to read or analyse rather than glance at — a CSV has no row limit at all, and it is the right tool for raw data. An image is for showing a table; a CSV is for working with one.
Good to Know
It loads in one pass. A dynamically sized table fetches its whole result set at once instead of filling columns in as you scroll, so it can take a moment longer to appear than a fixed-size table. That single load is what allows the widget to know how tall it needs to be.
Keep a browsing copy. If the same table is also something you look at day to day, put a normal Small or Medium copy of it on another tab and reserve the dynamically sized one for exporting.
The setting travels with the widget. Clone a dynamically sized table to another dashboard and the clone stays dynamically sized.
It is reversible at any time. Switching back to Small, Medium or Large restores the fixed frame and the drag handle; no data or configuration is lost.
If you have any questions, reach out to the Qvasa team — we are happy to help.