> 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/editable/working-with-editable/explore-data/group-rows-by.md). # Group Rows By The 'Group Rows' feature in EDITable lets you group the rows based on a selected column. Rows with the same attributes are grouped. 1. Click **Group** from the toolbar.

2. Select the column to group by. In the example below, we are grouping rows based on the department ID.

3. Within a group, you can create sub-groups. Click on **Add Subgroup** to create a subgroup.

4. Select another column to group them. We will select 'TargetBonus'.

Grouping by another column within a group

The results are as below:

5. Use the arrows to expand or collapse the groups and sub-groups.

6. Use the three-dot menu to expand all/collapse all or insert a row.

7. You can edit the table, and perform usual actions like formatting, bulk-editing, inserting rows, using find and replace, etc. on grouped rows too.

8. You can use the bin icon to ungroup a particular group. To return to the table, ungroup all of them by clicking delete on all groups.

--- # 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/editable/working-with-editable/explore-data/group-rows-by.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.