> For the complete documentation index, see [llms.txt](https://captivatehelp.newbluelive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://captivatehelp.newbluelive.com/play-and-update-graphics/chapter-index-1.md).

# Tables

Drive graphics from data you manage — CSV, Excel, Google Sheets, XML, or JSON — using Captivate’s general-purpose Tables controller.

Reach for Tables when your data can be treated as rows and columns, whether it comes from a spreadsheet, CSV file, Google Sheet, XML source, or JSON source. Tables: Row drives one record at a time, such as a player card or lower third — the most common path. Tables: Block drives several records at once, such as a leaderboard, roster, or schedule. This chapter covers the overview, the Row workflow, XML and JSON specifics, Block, and the specialized Crawls and Leaderboard controllers.

## What’s in this chapter

1. [Tables overview](/play-and-update-graphics/chapter-index-1/tables-overview.md) — what Tables does, when to use it instead of a catalog Data Controller, and how Row and Block differ.
2. [Drive a graphic with Tables: Row](/play-and-update-graphics/chapter-index-1/drive-a-graphic-with-tables-row.md) — the most common workflow: drive standard graphics from a spreadsheet, CSV, Google Sheet, XML, or JSON, one record at a time.
3. [Use XML or JSON with Tables](/play-and-update-graphics/chapter-index-1/use-xml-or-json-with-tables.md) — loading notes for XML and JSON feeds, and when the legacy controllers still apply.
4. [Tables: Block Controller](/play-and-update-graphics/chapter-index-1/tables-block-controller.md) — several records at once: leaderboards, rosters, schedules.
5. [Crawls Controller](/play-and-update-graphics/chapter-index-1/crawls-controller.md) — a ticker fed from a Tables source.
6. [Leaderboard Controller](/play-and-update-graphics/chapter-index-1/leaderboard-controller.md) — a ranked list (standings, top scorers) fed from a Tables source.

{% hint style="info" %}
If you maintain an older project that uses **General > Spreadsheet**, **General > JSON**, or **General > XML**, see [Legacy data controllers](/play-and-update-graphics/chapter-index-2.md).
{% endhint %}

## Related

* [Play and update graphics — section overview](/play-and-update-graphics/branch-index.md)
* [Data Controller catalog](/play-and-update-graphics/chapter-index-3.md) — use this instead when a specific live source provides the data, such as a scoreboard, weather service, presentation app, or meeting platform.
* [Legacy data controllers](/play-and-update-graphics/chapter-index-2.md) — pre-Tables Spreadsheet, JSON, and XML controllers.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://captivatehelp.newbluelive.com/play-and-update-graphics/chapter-index-1.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.