> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/flow/tutorials/components/data-table/tips-and-tricks/how-to-set-column-visibity.md).

# How to set column visibity

## Overview

In this step-by-step guide, we will explore configuring a column within the [**Avonni Data Table**](/flow/flow-components/data-table.md) component, based on particular criteria. We’ll demonstrate how you can effectively use flow variables to define these criteria, enabling a more dynamic and tailored presentation of your data within the table according to the specific conditions or requirements you set.

## Guided Steps

{% stepper %}
{% step %}

### Creating your flow Variable

That will be used as a variable to show or hide a column.

{% hint style="info" %}
***As an example***

**Example Formula:**

`{!Account.Industry}='Technology'`

**Implementation:**

Create a formula to determine if an Account's Industry field is 'Technology', and display a column in the Avonni Data Table accordingly, allowing users to view information relevant to Technology industry accounts only.
{% endhint %}
{% endstep %}

{% step %}

### Configuring the Data Source

To populate the Avonni Table, a Data Collection is required. You can achieve this by establishing a 'Get Records' collection.
{% endstep %}

{% step %}

### Drag the columns

Once your Data Source is configured, use it as a Data Collection to enable dragging columns derived from the 'Get Records' collection onto the Data Table.
{% endstep %}

{% step %}

### Activate the Hidden variable

* Open the '**Properties Panel**' and go to '**Data Source selection**' on the Avonni Data Table.
* Click on the desired column.
* Find the '**Hidden**' attribute and click the formula icon.
* Select '**Mapped**'.
* Choose your pre-created variable or formula to assign visibility. For example, if you have a variable named 'isVisible' with values true or false, select it here.

<figure><img src="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2Fgit-blob-0972d2dcf914da3621231fe7c7bbe688b1850de8%2F2023-09-30_15-19-21.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}


---

# 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.avonnicomponents.com/flow/tutorials/components/data-table/tips-and-tricks/how-to-set-column-visibity.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.