> 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/formula-syntax/identifiers/level.md).
# LEVEL
Retrieves the level of a row within a hierarchy.
The **LEVEL** identifier returns the row level in the hierarchy.
### Example
We have *Region*, *Country*, *State* and *Product Name* which denotes each level. The row grand total will be considered as 1st level followed by Region as 2nd level, Country as 3rd Level, State as 4th Level and Product Name as 5th level.
Calculating the level
For each city, we need to calculate the tax amounts based on level. Using the level formula, we get each hierarchy value and multiply it with the tax% value to arrive at the tax value.
Using the level column in a calculation
---
# 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/formula-syntax/identifiers/level.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.
