> 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/customize-tiles-sources.md).

# Customize tiles' sources

{% hint style="warning" %}
Warning

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

### Tile’s custom sources[¶](https://github.com/ToucanToco/doc-v3/blob/main/visualizations-and-layouts/creating-visualizations/advanced-chart-configuration/broken-reference/README.md)

Yes, you can have custom source based on data 😃 That means your source can come directly from your data source. Awesome!

To do so:

* you need to process a new data query under `source`
* the `field` property allows to select the default columns you want to access with `source`, it’s the column containing the source value
* Other columns present in the data are available with this syntax: `source.COLUMN_NAME`. i.e: your source is the country and the date, which are in two different columns.

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

Your source is the date.

**Data structure**

```coffeescript
| label      | value_ex | date | pays   |
|------------|----------|------|--------|
| Lorem      | 1        |10/16 | Paris  |
| ipsum      | 2        |11/16 | Lisboa |
| dolor      | 3        |12/16 | Rome   |
```

**Configuration**

```coffeescript
{
  name: "Metric"
  type: 'value-dynamic'
  value: "value"
  unit: "%"
  slide: 32204
  badge: 'badge'
  sentiment:
    value:
      domain: ['comparison']
      range: ['negative','positive']
  precision:
    value: '.1f'
  data:
    value:
      query:
        domain: "ranks"
      field: "value"
    source:
      query:
        domain: "ranks"
      field: ["date"]
  compute:
    badge: 'value - comparison'
  source: "Last update: <%= source.date %>"
}
```

### Ex2: Multiple sources

Your source is the country and the date, which are in two different columns.

**Data structure**

```coffeescript
| label      | value_ex | date | pays   |
|------------|----------|------|--------|
| Lorem      | 1        |10/16 | Paris  |
| ipsum      | 2        |11/16 | Lisboa |
| dolor      | 3        |12/16 | Rome   |
```

**Configuration**

```coffeescript
{
  name: "Metric"
  type: 'value-dynamic'
  value: "value"
  unit: "%"
  slide: 32204
  badge: 'badge'
  sentiment:
    value:
      domain: ['comparison']
      range: ['negative','positive']
  precision:
    value: '.1f'
  data:
    value:
      query:
        domain: "ranks"
      field: "value"
    source:
      query:
        domain: "ranks"
      field: ["date", "pays"]
  compute:
    badge: 'value - comparison'
  source: "Last update: <%= source.date %>, from <%= source.pays %>"
}
```


---

# 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://docs-v3.toucantoco.com/visualizations-and-layouts/creating-visualizations/advanced-chart-configuration/customize-tiles-sources.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.