> 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/december-2018/orders/automatically-retrieve-order-no.-and-order-date-in-sale-bill.md).
# Automatically Retrieve Order No. & Order Date In Sale Bill
**YouTube:** [Automatically Retrieve Order No & Order Date in Sale Bill](https://youtu.be/26BLDi5mMsQ)
### New Map SO Fields In Sale Voucher Configuration
When retrieving the Sale order in a Sale Bill, you may have noticed that it doesn’t display Sale Order No. & Sale Order date automatically. You have to manually enter the Order no. & Order Date, or Party Order No. & Party Order Date every time, which was time-consuming. That’s why, to automatically retrieve **order number & order date, or party order no. & party order date** in a sale bill, LogicERP included **Four new SO Fields** in Sale Voucher Configuration.
You can select either Order Number or Party Order Number at a time from SO Field. Same as in the case of order date or Party Order Date. When you select these fields, your Bill will automatically retrieve the sale order number and sale order date details.
---
# 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/december-2018/orders/automatically-retrieve-order-no.-and-order-date-in-sale-bill.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.
