> For the complete documentation index, see [llms.txt](https://docs.reportpundit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reportpundit.com/knowledge-base/report-creation/customized-reports/custom-fields/static-fields.md).
# Static Field
Static fields are useful when you want a row to contain a **constant / repetitive** **alphabetic, numeric, or alphanumeric** input. Numbers added in a static field will **not** be considered as a numerical value and can't be used for precise measurement. You can also avoid providing an input if required.
### :point\_right:Steps to Add a **Static Field**
1. Click on **Add Columns** in any report.
2. Click on **Add Custom Column.**
3. Select **Static Column** from the drop-down menu.
4. In the pop-up box, enter your **Field Name** and **Static Value** (fixed input) in the respective sections.
5. Click on **Add** to complete the process.
{% hint style="warning" %}
Remember to **Save** the report after adding the static column to retain it.
{% endhint %}
{% hint style="success" %}
:star2:That's it! You have successfully created a **Static Field** for your report.
{% 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.reportpundit.com/knowledge-base/report-creation/customized-reports/custom-fields/static-fields.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.