Validation error popovers now follow their fields when scrolling (EBS-14149)
Bug fix: When validation errors were displayed in Sales Desk after clicking Offer or Order Confirmation with missing required fields, the error popover remained fixed on screen while the page was scrolled. The popover did not move with its field, making it difficult to identify which field the error belonged to. This has been corrected. Error popovers now stay anchored to their respective fields at all scroll positions.
Warehouse search on article line now works correctly (EBS-16595)
Bug fix: When changing the warehouse on an individual article line in Sales Desk, the warehouse search field did not work as expected. On Draft orders, typing in the field did not filter the list — all warehouses were shown regardless of what was typed — and a recalculation pop-up appeared twice before it was possible to type anything. On Quote and Confirmed orders, the same premature recalculation pop-up interrupted the search. This has been corrected. The article-line warehouse field now works as a live type-ahead search in all order flows (Draft, Quote and Confirmed): typing filters the list immediately, and the recalculation pop-up no longer appears before the user has had a chance to type. When nothing is typed, all warehouses are shown.
Front page product search now displays the correct price group price (EBS-16636)
Bug fix: When searching for items on the front page in Sales Desk, the displayed price did not reflect the customer's price group — the base price was shown instead. The correct price group price was only applied once the item was actually added to the order, making the displayed price misleading. The root cause was that the warehouse number was not passed correctly to the price lookup. This has been corrected. The price shown in the front page search results now matches the price applied when the item is added to the order.
New order creation no longer blocked by sequence locking conflict (EBS-16697)
Bug fix: In some cases, creating a new sales order in Sales Desk failed with an "Already locked" error, completely blocking order creation. The root cause was a data inconsistency between the order sequence number and the locking service, caused by a transaction rollback that regressed the sequence counter while the corresponding lock remained committed. This has been fixed by ensuring the sequence number allocation is independent of the order save transaction, and adding a retry mechanism when a lock conflict is detected on new order creation.
Invoice type and payment terms now fall back to customer when blank on customer project (EBS-17001)
Bug fix: When creating a sales order in Sales Desk with a customer and a customer project, invoice type and payment terms were only retrieved from the customer project. If those fields were blank on the customer project, the order was created without invoice type and payment terms, causing the due date at invoicing to equal the invoice date. This has been corrected. Sales Desk now falls back to the customer's invoice type and payment terms when those fields are blank on the customer project. The fallback operates independently per field — if only one field is blank on the project, only that field falls back to the customer value.
Advanced article search now significantly faster in Sales Desk (EBS-17026)
Bug fix: The advanced article search in Sales Desk was consistently slow, with response times exceeding 15 seconds in production. The root cause was that the search ran two sequential full-collection scans against MongoDB, bypassing database indexes. The search has been rerouted through Elasticsearch, which is purpose-built for text search and uses an inverted index. Search response times are now well within acceptable limits.
Priority-based default email address selection when sending email from Sales Desk (EBS-17107)
New feature: When sending an email from Sales Desk, the default recipient email address is now selected based on a priority rule: the customer project email takes highest priority, followed by the contact person's email, and finally the customer card email as a fallback. If none of the sources contain an email address, the field is left empty. The priority logic is applied consistently across all entry points — Offer, Order Confirmation, and Send as email. The user can still manually override the pre-selected address.
Email address source now shown in the recipient dropdown when sending email from Sales Desk (EBS-17110)
New feature: When composing an email in Sales Desk, each address in the recipient (To) and copy (CC) dropdowns now shows its source in parentheses, for example: email@example.com (Customer), email@example.com (Project), email@example.com (Contact person), or email@example.com (Seller register). The source label is display-only and does not affect the recipient address itself. Project addresses are only shown when a project is selected on the order. The same email address may appear more than once if it is registered on multiple contacts or salespersons.
Item description lines no longer merged when saving orders in Sales Desk (EBS-17122)
Bug fix: When a sales order or quote was saved in Sales Desk, the item description on pre-existing order lines was incorrectly modified in NexStep. Specifically, the separator between item description line 1 and item description line 2 was lost, causing the two fields to merge into one. This occurred on any save operation — including saving without changes, adding a new line, or converting a draft to an order or quote. This has been corrected. Item description line 1 and line 2 now remain as separate fields after any save operation in Sales Desk.
Length specifications now stay correctly linked after reordering order lines (EBS-17123)
Bug fix: When order lines with length specifications were reordered in Sales Desk, the length specification records were not updated to reflect the new line numbers. This caused a mismatch between the order lines and their length specifications, which could result in incorrect data on orders, quotes, and PDFs. The fix ensures that length specification records follow their order lines correctly when lines are reordered, with no duplicate or orphaned records left behind. The fix also covers cases where an order is split during purchase order creation — length specifications are correctly transferred to the resulting child orders.
PDF printouts now show correct unit of measure for length specification lines (EBS-17179)
Bug fix: When generating quote or order confirmation PDFs from Sales Desk for order lines using length specification, the unit of measure on the length specification sub-rows was incorrectly displayed as "LM" instead of "STK". This has been corrected. Length specification sub-rows on both quote and order confirmation PDFs now correctly show "STK" as the unit of measure.
Order date now used for price lookup, and recalculated prices correctly saved to ERP (EBS-17192)
Bug fix: Two related pricing issues have been corrected in Sales Desk:
First, when fetching prices for an order line, the order date was not taken into account — the latest available price was always used regardless of the order date. Prices are now fetched from the price table valid at the order date, so backdated or future-dated orders get the correct price for that date.
Second, when the order date was changed on an order that already had lines and the user chose to recalculate prices, the recalculated price was shown correctly in the UI but the original price was sent to NexStep ERP on save. This has been corrected. The recalculated price is now the price that is saved and transferred to ERP. Choosing to keep existing prices still works as before.