> 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/setups/configurations/sale-voucher-configuration/other-settings-1/other-settings/defaults-2/expression.md).

# Expression

**YouTube:** [How to Configure and Use Expression Functions in Sale Bill?](https://www.youtube.com/watch?v=oOsuVpBZWEw)

## How to Configure and Use Expression Functions in Sale Bill?

In this tutorial, we’ll demonstrate how to **set default expressions for generating a sales bill** in **Logic ERP**, allowing fields like **Remarks** to populate automatically based on user-defined expressions.

***

### **Access Sales Voucher Configuration**

* Open the **Sales Voucher Configuration** window.
* Select the **relevant billing series**.
* Under **"Other Settings - 1"**, click on **"Other Settings"**.
* Then navigate to **"Defaults - 2"**.
* Locate the option labeled: “**Expression”**.
  * Here, you can define **custom expressions** using the available field list.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FWcOD0OGejeK65vUy6dkC%2FExpression.png?alt=media&amp;token=31a96889-ce13-4704-b727-07b823eb3f75" alt=""><figcaption></figcaption></figure>

***

### **Create a Default Expression**

* Let’s create a default expression for the **Remarks One** field.
* In the expression editor, combine fields such as:
  * **Transport Mode**
  * **Vehicle Number**

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FicURapyPh4I3h7c6My21%2FExpression%20Default.png?alt=media&amp;token=4b1d2fa4-5df1-435a-bafc-47dcbebcdbb2" alt=""><figcaption></figcaption></figure>

* Save the configuration after setting the expression.

***

### Functionality in the Billing Process

* Navigate to the **Sale Bill** window.
* Enter the **Transport Mode** and **Vehicle Number** in Other Details Column.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FvkjiLnPmJO4k85raTN7D%2FOther%20Detailns%20in%20billing.png?alt=media&amp;token=ec92206f-0d60-4108-aa6e-f489f2b5cd89" alt=""><figcaption></figcaption></figure>

* Proceed to **save the bill**.

***

### Observe the Applied Changes

* Reopen the saved bill.
* Navigate to the **Other Details** section.
* Observe that the **Remarks One** field is **automatically populated** with the values entered for transport mode and vehicle number.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FBaYGHe4qk5Z3otCqavo0%2FRemark.png?alt=media&amp;token=39b2c723-e28b-43a5-b392-2f869a9ee806" alt=""><figcaption></figcaption></figure>

***

### **Conclusion**

Using default expressions in Logic ERP allows for **automated data entry**, reducing manual effort and ensuring consistency across sales bills.


---

# 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/setups/configurations/sale-voucher-configuration/other-settings-1/other-settings/defaults-2/expression.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.
