by John Tomasino (FL)

Like many appellate clerk offices, we rely heavily on Tableau to report on case data drawn from our case management systems. These reports are often shared in PDF format with judges and court leadership, where presentation matters as much as accuracy.

Recently, I encountered a familiar problem: a table-based Tableau report that looked fine on screen but exported poorly to PDF. Specifically, when printed in landscape format, the table refused to properly fill the page width. The result was a report with awkward white space, inconsistent scaling, and less-than-ideal readability.

This is not an uncommon issue. Tableau’s behavior when moving from on-screen display to PDF output is not always intuitive. Settings that seem like they should control layout—such as “Fit” options—often interact in unexpected ways with dashboard sizing and export behavior.


The Challenge

The report in question contained a wide table of case information—case numbers, titles, dates, authorship, and other attributes. When exported:

  • The table did not fully utilize the available page width
  • Adjusting settings like “Entire View” caused rows to compress and overlap
  • Manually widening columns created new problems, including excessive pagination

In short, each attempted fix solved one problem while creating another.

Initial PDF output. Despite using landscape orientation, the table does not expand to fill the available page width, leaving significant unused space and reducing readability.

The Constraint

Although with best intentions of supporting the extensive Tableau reports used by the appellate clerks, the office of information technology within the state court administrator’s office was stretched thin with legislatively mandated projects and technology needs from the 20 circuits and 67 counties in Florida. The appellate courts are looking to augment resources for our reporting needs, and one great partner turns out to be ChatGPT.


The Approach

Rather than continuing trial-and-error adjustments, I used ChatGPT to diagnose the issue and walk through the competing layout constraints in Tableau.

The key insight was this:

Tableau does not dynamically optimize reports for PDF output. It scales what you design—it does not redesign it.

That distinction drives everything.


The Solution

The working solution involved a combination of small but important adjustments:

1. Use the Right Fit Setting

Set the worksheet to:

  • Fit → Fit Width

This allows the table to expand horizontally without compressing rows vertically (which occurs with “Entire View”).


2. Set a Fixed Dashboard Size

Use a fixed size such as:

  • Letter Landscape (approx. 1100 × 850 pixels)

This ensures Tableau is designing for a known output target instead of a variable screen size.


3. Avoid Overcorrecting Column Widths

Attempting to force the table to span the entire width by aggressively widening columns led to excessive page counts.

Instead:

  • Keep columns reasonably sized
  • Allow for some right-side margin
  • Prioritize readability over edge-to-edge layout

4. Optimize Row Density

To reduce page count without sacrificing structure:

  • Use Format → Cell Size → Shorter
  • Slightly reduce font size where appropriate

This allows more rows per page without distorting the layout.


5. Clean Up Layout Artifacts

Remove unnecessary padding or blank containers in the dashboard, which can introduce misleading whitespace in the final PDF.


The Result

The final report:

  • Uses the available page width effectively
  • Maintains readable row spacing
  • Produces a clean, multi-page PDF without distortion

Why This Matters

This exercise highlights a broader point. Tools like Tableau are powerful, but their behavior—especially around layout and export—can be opaque. What appears to be a simple formatting issue can involve multiple interacting settings with no obvious solution.

AI tools like ChatGPT can serve as a practical supplement in these situations:

  • Explaining how the software actually behaves
  • Identifying root causes rather than symptoms
  • Reducing time spent on trial-and-error

A Practical Takeaway

When working with Tableau for printable reports:

  • Design for the output format, not just the screen
  • Avoid “Entire View” for long tables
  • Balance width, readability, and pagination—Tableau will not do it for you