> 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-learning-hub-tutorials-and-best-practices/order-processing/generate-delivery-orders/generate-delivery-orders-configuration/show-data-for-current-branch-only.md).
# Show Data for Current Branch Only
**YouTube:** [How to Filter Sales Orders by the Logged-In Branch in Delivery Orders?](https://youtu.be/A6tZtZzfdB4)
## How to Filter Sales Orders by the Logged - In Branch in Delivery Orders?
In this tutorial, we will learn how to **display data only for the currently logged-in branch** while creating a Delivery Order in Logic ERP.
***
### Understand the Default Behavior
* Initiate a new **Delivery Order** entry.
* Click on **Sales Order Selection**.
**Result**
By default, the search list displays **all available Sales Orders**, including those created in the current branch as well as other branches.
***
### Enable Current Branch Data Filter
* Open the **Delivery Order Configuration** window.
* Navigate to the **General Settings** section.
* Locate and enable the option labeled as:
> **"Show Data for Current Branch Only"**
* Save the configuration changes.
**Verify the Configuration**
* Reopen the **Delivery Order** window.
* Initiate a new entry.
* Click on **Sales Order Selection**.
**Result**
The Sales Order search list now displays **only the Sales Orders belonging to the currently logged-in branch**.
For example, if the logged-in branch is **Head Office (HO)**, only Sales Orders created under the **HO branch** will be displayed.
***
### Key Benefits
* **Branch-Wise Data:** Displays only relevant branch transactions.
* **Improved Control:** Prevents users from accessing Sales Orders from other branches.
* **Easy Selection:** Makes Sales Order selection faster and more organized.
* **Better Data Management:** Helps maintain branch-specific transaction workflows.
---
# 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-learning-hub-tutorials-and-best-practices/order-processing/generate-delivery-orders/generate-delivery-orders-configuration/show-data-for-current-branch-only.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.
