> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/working-with-inforiver/4.-adding-business-logic-and-formulae/visual-column-inside-visual-measures.md).
# Visual column inside visual measures
We have covered the different types of manual input columns that can be inserted in the report in the previous sections. We have also learned the steps to [insert calculated columns](/working-with-inforiver/4.-adding-business-logic-and-formulae/insert-calculated-columns.md), in the form of visual measures as well as visual columns.
In this page, we will look at a specific case where you can include a data input visual column to be referenced inside a visual measure formula.
Data fields like interest rates, discount rates, tax slabs, and foreign exchange rates might be common to all the column dimensions. Hence they would be created as visual columns and we might need to refer to them often in calculations. In such cases, you can reference those visual columns in visual measures using the **COLUMNS** prefix.
Let us consider the following example: a visual input column is included to specify a discount rate of 10%.
Visual Column - Discount%
To calculate the new sale price, we can insert a formula measure.
Inserting formula measure
In the formula, we need to refer to this visual column, **Discount*****%*** to calculate the discounted sale price. The visual column is referred to using the **COLUMNS** prefix identifier.
Visual column referred inside a visual measure
Click **Create** and the result is shown below:
Discounted Price
{% hint style="info" %}
In the current edition, visual measures can only refer to **data input** visual columns and not calculated visual columns (formula columns).
{% endhint %}
---
# 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.inforiver.com/working-with-inforiver/4.-adding-business-logic-and-formulae/visual-column-inside-visual-measures.md?ask=&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.
