# Datafield aliases

When you create a name for a datafield, you will do this in the language of your choice. However, it may be desirable to provide translations for this name if you are in the habit of uploading clauses in multiple languages. That is where aliases come in.

Aliases allow you to give additional names to datafields and tie them to a specific language. This allows you to refer to the same datafield with different names. When you, for example, use the English alias of a datafield in the Dutch version of a clause, you will be given the opportunity to automatically “translate” the English alias to the Dutch alias. In the example below, this can be done by clicking *“to nl”*

<figure><img src="/files/HuuUMmS6rIhw5JtJhrqW" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="info" %}
Don’t confuse the **alias** with the **label** of the datafield. The **label** is only used within the user interface, towards end-users — unlike the datafield’s name and alias, the label can for example contain spaces, parentheses, or whatever else you want that best communicates the purpose of the datafield towards your end-users.

For example, if you have a datafield `#customer^address-nr` in English, you may want to translate this into `adresse-numéro` in French by creating a French alias. In the French body of your clause, you can then refer to that datafield as `#customer^addresse-numéro` .

However, towards your end-users, *“address-nr”* and *“adresse-numéro”* are not particularly friendly — you could therefore create a label *“address and number”* in English and *“adresse et numéro”* in French.
{% endhint %}


---

# 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://help.clause9.com/datafields/datafield-aliases.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.