--- title: "EG Fabri SalesDesk v2.1.0" slug: "release-notes-eg-fabri-salesdesk-v210" updated: 2025-12-09T14:10:10Z published: 2025-12-09T14:10:10Z canonical: "products.egfabri.cloud/release-notes-eg-fabri-salesdesk-v210" --- > ## Documentation Index > Fetch the complete documentation index at: https://products.egfabri.cloud/llms.txt > Use this file to discover all available pages before exploring further. # EG Fabri SalesDesk v2.1.0 ### Modal Workflow ([EBS-12365](https://jira.eg.dk/browse/EBS-12365?src=confmacro)) - When creating an offer or order confirmation, users see a modal with two options: **Print** and **Email**. - Selecting **Email** opens a dedicated **Email Editor** modal after the document is created, giving users full control over the message before it is sent. ### Enhanced Email Editor - The Email Editor now automatically loads customer email addresses from the customer record. - Users can easily select or deselect which recipients should receive the message. - Both the **email subject** and **email body** can be edited and customized, enabling more tailored and professional communication. ### Issue: Updated project name is not displayed in the generated document ([EBS-13570](https://jira.eg.dk/browse/EBS-13570?src=confmacro)) Previously, when a user updated the **Project Name** under the **Customer and Project** section and sent an email from the **Sales Order** details page: - The **email subject** in the preview did not reflect the updated Project Name. - The **attached document** in the email received by the recipient could be incorrect or outdated. ### **Resolution** The issue has been fixed. Now, when a user updates the Project Name and sends an email: - The **email subject** correctly displays the updated Project Name. - The **attached document** in the sent email matches the current Sales Order details. ### Issue: Change to purchase unit for items from Solve Calculator ([EBS-13678](https://jira.eg.dk/browse/EBS-13678?src=confmacro)) Previously, when fetching items from **Solve Supply item Calculator**, if the **unit added in the Sales Order** differed from the **purchase unit**, **no conversion or calculation** was applied. This caused incorrect or missing quantity and pricing information. ### **Resolution** The issue has been fixed. Now: - **Unit conversions** between the Sales Order unit and the purchase unit are correctly executed. - **Calculations** between different units are accurately presented in the Sales Order. ### **Impact** Users can now fetch items from Solve Supply item Calculator and create Sales Orders with units differing from the purchase unit, with accurate conversions and calculations automatically applied. ### Enhancement: Persistent Selection Across Advanced Search Pages ([EBS-13752](https://jira.eg.dk/browse/EBS-13752?src=confmacro)) SalesDesk now supports selecting products across **multiple pages** in the Advanced Search results. Users can: - Select products on one page - Navigate to the next or previous page - Continue selecting additional products - Add **all selected items** to the cart in a single action Previously, quantities and selections were cleared when moving to the next page. This issue has been resolved, ensuring a smooth and consistent product-picking workflow. ### Enhancement: All numeric fields with Up to Two Decimals ([EBS-13757](https://jira.eg.dk/browse/EBS-13757?src=confmacro)) SalesDesk now supports entering **all numeric fields with values including up to two decimals** on item lines. This improvement allows users to: - Set **precise quantity and prices or DG values** when adding items to an order - Achieve exact pricing and margin control - Ensure consistency between calculated DG and the DG displayed on the order line ### Discount recalculation now works as expected ([EBS-13806](https://jira.eg.dk/browse/EBS-13806?src=confmacro)) A correction has been applied to ensure that the recalculation logic processes **all matching article lines**, regardless of duplicates. Price and discount recalculation now updates each occurrence of the article as expected. ### Issue: Existing contact persons showing up as " null" ([EBS-13815](https://jira.eg.dk/browse/EBS-13815?src=confmacro)) Previously, when selecting an existing contact person, a "null" value could appear after their name, causing incorrect display on documents. ### **Resolution** The issue has been fixed. Now: - Existing contact persons are displayed **without “null” appended**. - Documents (quotes, orders, invoices) show the **correct contact person name**. ### **Impact** Users can now reliably select contact persons without any formatting errors on documents. ### Issue: Wrong vendor on salesline before creating PO ([EBS-13873](https://jira.eg.dk/browse/EBS-13873?src=confmacro)) Previously, when creating a **new Sales Order (SO)** and adding an item from **Purchase Goods (Solve Supply item Calculator)**, then saving the SO as an **Offer** or **Order Confirmation**: - The SO was saved with the **“NOBB price vendor”** instead of correct **ledger vendor**. ### **Resolution** The issue has been fixed. Now: - When creating an SO and adding items from **Purchase Goods (Solve Supply item Calculator)**, the SO is saved with the **correct vendor (ledger vendor)**. ### **Impact** Users can now rely on **accurate vendor information** when saving Offers or Order Confirmations, ensuring consistency in procurement and reporting. ### Issue: Incorrect unit conversion on item ([EBS-13900](https://jira.eg.dk/browse/EBS-13900?src=confmacro)) When the **base unit** of an item has a **conversion factor other than 1**, there was a problem with the **correct calculation and presentation** of quantities between units (e.g., **M2 → STK → PAK**). ### **Resolution** The logic for **handling unit conversions** in such cases has been implemented. Now: - Calculations between units (M2, STK, PAK) are **correctly executed and displayed**, even when the base unit conversion factor is not 1. ### **Impact** Users can now rely on **accurate quantity conversions and presentations** for items with base units that have non-standard conversion factors. ### Issue: Add validation on amount * price in saleslines ([EBS-13959](https://jira.eg.dk/browse/EBS-13959?src=confmacro)) Previously, when creating or editing a **Sales Order**, entering an unusually large quantity on an item line (e.g., **NOBB number**) caused the order import into N**X** to fail. - **Expected behavior:** The system should prevent saving item lines with excessively large quantities. - **Actual behavior:** The order could be saved, but import failed due to **excessive calculation size**. ### **Resolution** The system now **prevents users from saving item lines** with excessively large quantities, ensuring: - Sales Orders cannot exceed system calculation limits. - Imports into N**X** succeed without errors. ### **Impact** Users are now guided to enter **valid, manageable quantities**, avoiding errors during sales order processing and imports.