> For the complete documentation index, see [llms.txt](https://docs-v3.toucantoco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-v3.toucantoco.com/visualizations-and-layouts/creating-visualizations/advanced-chart-configuration/manage-data-order-in-your-tiles.md).

# Manage data order in your tiles

How to :: manage data order in your tiles

### Overview

You can force a certain layout/order of your insights in your tiles. By default, it will be the alphabetical order.

📝 I’m analyzing the number of people visiting my mall by day. So I’d would like to order my data by the day of the week. The day of the week are contained in the `label` column of my data file.

### Sort values[¶](https://github.com/ToucanToco/doc-v3/tree/main/visualizations-and-layouts/creating-visualizations/advanced-chart-configuration/broken-reference/README.md)

For some tiles you can select a default order from the **tiles parameters** menu. Ascendant or descendant.

📝 Do I want to identify first the worst performers? or the best ones? What decision should I be able to make?

<figure><img src="https://1809014303-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZxYYf1KpgarKMgMsDCrw%2Fuploads%2Fgit-blob-777f0811cd3840d7a9119c07e1108464e177849c%2Fsort-tiles.gif?alt=media" alt="sort tiles"><figcaption><p>sort tiles</p></figcaption></figure>

### Configure order from a column[¶](https://github.com/ToucanToco/doc-v3/tree/main/visualizations-and-layouts/creating-visualizations/advanced-chart-configuration/broken-reference/README.md)

{% hint style="info" %}
Warning

This is only available from the code mode.
{% endhint %}

From the code mode you can also set the order of your values from a column.

Add an **order by** parameter. Fill the `""` with the name of the column containing the order. It can be a `int` or `str` column, by default it will be `asc` and alphabetical order.

```coffeescript
order:
  by: ""
```

### Configure order from a list

{% hint style="info" %}
Warning

This is only available from the code mode.
{% endhint %}

From the code mode you can also manually set the order of your values.

Add an **order custom** parameter. Fill the `[""]` with the literal value of the label/group/pack. Separate values with `,` and add them in the order you wish them to be displayed.

```coffeescript
order:
  custom: [""]
```

📝 I want to see Paris first, what ever the value is. I would use :

```coffeescript
order:
  custom: ["Paris"]
```

📝 I want to see Paris first, then Monaco, what ever the values ares. I would use :

```coffeescript
order:
  custom: ["Paris", "Monaco"]
```


---

# 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-v3.toucantoco.com/visualizations-and-layouts/creating-visualizations/advanced-chart-configuration/manage-data-order-in-your-tiles.md?ask=<question>&goal=<user_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.
