> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-version-release-notes/november-2019/billing/limiting-maximum-allowed-rows-in-data-entry-grid-window.md).

# Limiting Maximum Allowed Rows in Data Entry Grid Window

YouTube: [Limiting Maximum Allowed Rows in Data Entry Grid Window](https://youtu.be/U5GNJkAR-Mw)

Now you can configure the number of rows to be allowed in the data entry grid window. A new option added to limit the number of rows in the data entry grid. With the “**Maximum allowed rows in Data Entry**” option, you can limit the number of rows in the data entry grid.[<br>](https://www.logicerp.com/tutorials/wp-content/uploads/2019/02/Maximum-allowed-rows-in-data-entry.png)

<figure><img src="/files/9vVeuSgb4qhFENXKdUo9" alt=""><figcaption></figcaption></figure>

After setting the limit, if the user will try to exceed the limit, the following message will display on the screen:

<figure><img src="/files/1ZW8BBhkntKVcboysH1H" alt=""><figcaption></figcaption></figure>

Note: This option will not work in case of ‘Retrieve Challan’ & ‘Retrieve Order’ case.


---

# 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://kb.logicerp.com/logic-erp-version-release-notes/november-2019/billing/limiting-maximum-allowed-rows-in-data-entry-grid-window.md?ask=<question>&goal=<endgoal>
```

`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.