> 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/sale-order/so-configuration/expression-for-other-details.md).
# Expression For Other Details
**YouTube:** [How to Configure Expressions / Formulas for Other Details in Sales Orders?](https://www.youtube.com/watch?v=JMHuq5mp7qk)
## How to Configure Expressions / Formulas for Other Details in Sales Orders
In this tutorial, we will learn how to create and use **Expressions for the Other Details** section in Sales Orders. This feature allows you to automatically calculate field values based on predefined formulas, reducing manual calculations and ensuring consistency during order entry.
***
### Objective of This Feature
* Automate calculations in the **Other Details** section.
* Eliminate manual data entry.
* Ensure consistent field values.
* Reduce calculation errors.
* Improve Sales Order entry efficiency.
***
### Access to the Sales Order Configuration
* Go to the **Sales Order Module**.
* Click **Configuration**.
* Select the required **Sales Order Configuration**.
* Locate the option labeled as:
> **"Expression For Other Details"**
* This screen allows you to create expressions using the available field list.
**Example**
* Let's create an expression for **TD%**.
* Configure the expression as:
* **TD% = CD% − 2**
* This means the system will automatically calculate the **TD%** by subtracting **2** from the entered **CD%** value.
* After defining the expression, save the configuration.
***
### Observe the Functionality
* Click **New Order** to refresh the Sales Order window.
* Create a new Sales Order.
* Open the **Other Details** section.
* Enter a value in the **CD%** field.
**For example:**
* **CD% = 5**
Click **OK** to save the details.
**Result**
Open the **Other Details** section again.
The **TD%** field is automatically populated based on the configured expression.
In this example:
* **CD% = 5**
* Expression: **TD% = CD% − 2**
* **TD% = 3**
The system automatically performs the calculation and updates the **TD%** field, confirming that the expression has been successfully applied.
***
### Key Benefits
* Automates field calculations.
* Reduces manual effort during order entry.
* Ensures consistent business rule implementation.
* Minimizes calculation errors.
* Improves data accuracy and productivity.
***
### Best Practice Tips
* Verify the expression logic before saving the configuration.
* Use the available field list to build accurate formulas.
* Test expressions with sample transactions before deploying them in production.
* Keep expressions simple and aligned with your business requirements for easier maintenance.
***
### Final Outcome
The **Expression For Other Details** feature enables Logic ERP to automatically calculate values in the **Other Details** section based on predefined formulas. By configuring expressions such as **TD% = CD% − 2**, the system performs calculations automatically during Sales Order entry, improving accuracy, consistency, and overall efficiency.
---
# 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-learning-hub-tutorials-and-best-practices/order-processing/sale-order/so-configuration/expression-for-other-details.md?ask=&goal=
```
`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.