> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/analytics+/working-with-analytics+/8.-splitting-and-grouping-measures/splitting-and-grouping-tables.md). # Splitting and grouping: tables In this section, we'll discover the various options in Inforiver to split and group measures in Table mode. ### 1. Splitting measures When you have multiple measures and categories in your table, you can display each measure in a separate panel. Click on the **Split** button in the toolbar.

Notice each measure is displayed as a separate table when splitting is enabled.

### 2. Measures category When the split option is enabled a **measures category** is created: the measures can be rendered as rows or columns. We've added a Sub Region as a small multiple parameter to demonstrate the measures category feature. Notice how the measures are rendered as separate rows when the split option is enabled.

The image below shows the measures rendered as columns.

### 3. Grouping measures With the Group feature, you can create visual-level column hierarchies in a single click. All you need to do is select the measures to be grouped, click the **Group** button, and enter the name of the custom group in the textbox.

We've grouped the Actuals and Plan into the 2024 and 2023 buckets.

You can **expand and collapse** column groups with the

icons just as you would with regular hierarchies from the dataset.

To delete a group, select it and click **Remove**.

--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.inforiver.com/analytics+/working-with-analytics+/8.-splitting-and-grouping-measures/splitting-and-grouping-tables.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.