> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/dataprep/transforming-data/aggregate.md).

# Aggregate

In this document, you will explore how to aggregate in Astera Dataprep.    

1. To aggregate in Astera Dataprep, you can click on the *Transform* option in the toolbar and select *Aggregate* option from the drop-down.

![](/files/yoLieVGKaXwfz23FRs19)

2. Once selected, the *Recipe Configuration – Aggregate* panel will open. 

![](/files/jqI6q9BcyT0VXzLxZ25o)

3. Here, you can configure the *Aggregate* section by selecting column names in the *Name* drop-down, adding any expressions in the *Calculation* column, and selecting an *Aggregate Function* from the drop-down with all the aggregate functions.

![](/files/64Uc6iYhy8oT18xH9k25)

4. Once done, you can click on *Apply* ![](/files/10KTRq7DN4pST0pzbGYQ)

Now, in the grid, you can see that the columns have been grouped by the *EmployeeID* and a *Count* aggregate function has been applied to the *OrderID* field.

![](/files/cNUhzYKfhpaitiydyuOe)

This concludes the document on using *Aggregate* in Astera Dataprep.


---

# 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://documentation.astera.com/dataprep/transforming-data/aggregate.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.