> 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/may-2026/billing/order-date-column-enabled-in-enter-gr-details-grid-mode.md).

# Order Date Column Enabled in Enter GR Details - Grid Mode

Logic ERP has introduced a new enhancement to the **Enter GR Details – Grid Mode** feature.

Previously, the **Order Date** entered in the **Sales Bill** was not visible in the **Enter GR Details – Grid Mode** window, requiring users to reopen the Sales Bill for verification.

With this update, a dedicated **Order Date** column has been added to the grid, allowing users to view the Order Date directly during GR processing, making the workflow faster and more convenient.

***

### **Step 1: Verify the Order Date in the Sales Bill**

Before proceeding, let's first verify the **Sales Bill** in which the **Order Date** has already been defined.

* Open the **Sales Bill**.
* As shown, the **Order Date** has already been entered in the document.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FdKo7rsPq9dmalfeZfRQu%2FCNF.png?alt=media&amp;token=36a0d4c2-b55f-41b0-9634-20a0f986594a" alt=""><figcaption></figcaption></figure>

This is the same Order Date that we will display in the **Enter GR Details – Grid Mode** screen.

***

### **Step 2: Enable the Order Date Column**

Now, open the **Enter GR Details – Grid Mode** module.

* Click on **Set Column Attributes**.
* In the list of available columns, locate the **Order Date** field.
* Enable the **Order Date** column.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2F1TnpLy5xZlcOlJMfp990%2FSet%20Column%20Attribute.png?alt=media&amp;token=a0bcc3a2-7e43-495b-b537-0934e10a6bec" alt=""><figcaption></figcaption></figure>

* Click **Save** to apply the changes.

***

### **Step 3: Review the Impact**

* Once the settings are saved, the **Enter GR Details – Grid Mode** screen will refresh.
* As you can see, the **Order Date** defined in the corresponding **Sales Bill** is now automatically displayed in the **Order Date** column.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FIEBXtn2kpgMycxTBpzE5%2FOrder%20Date.png?alt=media&amp;token=e7943044-dbc8-40fd-b0a2-4ef47ece2372" alt=""><figcaption></figcaption></figure>

This allows users to easily view and verify the Sales Order Date directly while processing GR entries, improving visibility and reducing the need to open the original Sales Bill.


---

# 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://kb.logicerp.com/logic-erp-version-release-notes/may-2026/billing/order-date-column-enabled-in-enter-gr-details-grid-mode.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.
