> For the complete documentation index, see [llms.txt](https://videos.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://videos.inforiver.com/reporting-matrix/planning-budgeting-and-forecasting/manual-data-input.md).

# Manual data input

With Inforiver, you can allow report designers and consumers (in reading view) to insert, edit and update values in your tabular reports. In this video, learn how you can 

(a) Enter data in different formats such as number, text, checkbox, single/multi-select and date 

(b) Enter formulas instead of absolute values 

(c) Leverage 50+ in-built functions (logical, math, boolean etc.,), keywords and references while creating your formula 

(d) ​Allow data input only for certain rows based on a condition/formula that you determine (e.g., Margin <10%)&#x20;

(e) Allow multiple users in the organization to enter data in the reading view​

{% embed url="<https://lumel.wistia.com/medias/hn2odsnae0>" %}

> ## **Related resources**
>
> #### Feature highlights
>
> [Input and edit data in Power BI](https://inforiver.com/input-edit-data-powerbi/)
>
> #### User guide
>
> [Insert manual input columns](https://docs.inforiver.com/working-with-inforiver/4.-adding-business-logic-and-formulae/insert-manual-input-columns)
>
> #### Blog
>
> [5 types of manual data entry options in your Power BI table/matrix](https://inforiver.com/blog/writeback/5-types-manual-data-entry-powerbi-table-matrix/)


---

# 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://videos.inforiver.com/reporting-matrix/planning-budgeting-and-forecasting/manual-data-input.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.