> For the complete documentation index, see [llms.txt](https://usermanual.ergonode.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://usermanual.ergonode.com/product-design/attributes/attribute-variables.md).

# Attribute variables

Insert the value of one attribute into a text area attribute as a variable, with the attribute types allowed and the limits that apply.

{% embed url="<https://www.youtube.com/watch?v=lhXC8Jh26us>" %}

{% hint style="info" %}
Additional information:

* Variables are allowed for text area type attributes only
* If the user does not have privileges to preview an attribute, then instead of attribute code (e.g. #color) they see a placeholder with the text “No access”
  {% endhint %}

{% hint style="info" %}
Information for apps developers: our app engine does not support the cases listed below:

* uses of global attributes with local attributes used as variable
* uses of global attributes with local select type attributes
* refreshing values of a variable when changing a transition of the option value in the select type attribute
* When working with variables via API, remember to put them in double brackets Ex: {{#attribute\_code}} so the system knows they're variables, not a string
  {% endhint %}

{% hint style="info" %}
In Ergonode Transfer when working with variables in text area attribute (products.csv), remember to put them in double brackets Ex: {{#attribute\_code}} so the system knows they're variables, not a string.
{% endhint %}

### Types of attributes that can be added as a variable:

* date
* select (multi select attributes can't be used)
* numeric
* text
* price (only value, without currency)
* unit (only value, without unit)

### **Areas where you can edit the attributes with variables** <a href="#spaces-in-which-we-can-edit-the-attributes-with-variables" id="spaces-in-which-we-can-edit-the-attributes-with-variables"></a>

* [product template](https://usermanual.ergonode.com/products/catalog/template#attribute-variables-in-the-product-template)
* catalog table (grid)
* [batch actions](https://usermanual.ergonode.com/products/catalog/batch-actions)
* import - in order to import a variable you need to enter it in the appropriate {{#attributecode}} format
* [export](https://usermanual.ergonode.com/system/ergonode-transfer/exports/creating-a-new-export) - configuration of whether we download data with variables or final resolved content

If you are using attribute variables it's possible to use them directly on the grid.

On the grid, double click on the attribute to open it to edit. If the attribute isn't shown in the grid, add it as a column first, see [Custom views](https://usermanual.ergonode.com/products/catalog/system-views/custom-views).

<figure><img src="https://171427267-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM9BbYBbDPiJapb75xJ2k%2Fuploads%2FO1vnUpuMC5dacqHqjNcy%2F314c7f678874.png?alt=media&amp;token=8475f5a1-44d3-4ae2-be81-8c77d8bb9c23" alt=""><figcaption></figcaption></figure>

Type hash char (#), and you will be presented with a list of attributes you may use. A globe icon marks a global attribute.

<figure><img src="https://171427267-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM9BbYBbDPiJapb75xJ2k%2Fuploads%2Fzk9Lm3EVFhgIwq9w6VnU%2F657426bba6b1.png?alt=media&amp;token=6c9dc177-2b73-4852-b82f-3217709bb04b" alt=""><figcaption></figcaption></figure>

Type more to narrow the list.

<figure><img src="https://171427267-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM9BbYBbDPiJapb75xJ2k%2Fuploads%2FcQZngokxBStCTuNQqJQ6%2F4d782e90027b.png?alt=media&amp;token=0c4d98bd-66eb-49a4-9227-a10913530768" alt=""><figcaption></figcaption></figure>

You may use more than one variable.

<figure><img src="https://171427267-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM9BbYBbDPiJapb75xJ2k%2Fuploads%2FvKRkfxEAQHb7l798Xqfd%2Fimage.png?alt=media&#x26;token=42d1930a-fc3a-492e-95bb-894bbcd4448a" alt="" width="563"><figcaption></figcaption></figure>

When variables are used, an eye icon appears in the upper right corner of the field while you point at it. Clicking it will display a preview of the values.

<figure><img src="https://171427267-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM9BbYBbDPiJapb75xJ2k%2Fuploads%2Fn56B2t2GnAhGZmItPGnQ%2Fimage.png?alt=media&#x26;token=c96a2c1e-27fc-4ba2-9189-75ce58d09ccb" alt="" width="563"><figcaption></figcaption></figure>

<figure><img src="https://171427267-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM9BbYBbDPiJapb75xJ2k%2Fuploads%2FkjX4DB80bNUCifm6KFgJ%2Ff951fd276af6.png?alt=media&amp;token=e75305fa-47c7-4236-877d-65bf5ab05865" alt=""><figcaption></figcaption></figure>


---

# 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://usermanual.ergonode.com/product-design/attributes/attribute-variables.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.
