# Explorer

<figure><img src="/files/JLMYBvqCOONdCuwLAnHR" alt=""><figcaption></figcaption></figure>

Explorer allows you to perform common data transformations via a graphical user interface while viewing the data. Explorer can be used on the execution results of the SQL Block or Charts in notebook and report.

## Key Features

* Spreadsheet-like UI and Drag-and-drop UI:
  * Sort, filter, and select values from column headers just as in a spreadsheet.
  * Select fields, apply filters, and sort data using drag-and-drop.
* Aggregation:
  * Perform simple aggregations (Group by) using drag-and-drop.
* Field Statistics:
  * Check statistical information from column headers.
* Chart Recommendation:
  * Generate recommended charts based on the type and form of the operation results.

## Where Explorer is Available

Since Explorer interacts directly with the original data, it’s available only in certain contexts.

* Notebook (DocPage/GridPage)
* Report
  * When `Report type` is `Interactive report`, and `Enable explorer` is selected in the Options
* Signed Embed
  * When `Enable explorer` is selected in the Options

Please refer to this section for further details.

{% content-ref url="/pages/q3VlGEYQbem4hJ652fGL" %}
[Sharing Overview](/sharing/sharing-overview.md)
{% endcontent-ref %}

## In-Memory Processing

* In Explorer, if the target data is within 1000 rows and no custom SQL is used, the in-memory processing processes data on the user's browser without issuing a new query.
* This processing can be disabled by checking the `Disable in-memory processing` checkbox.


---

# Agent Instructions: 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:

```
GET https://docs.codatum.com/data-exploration/explorer.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.