Monday, April 28, 2025
3 changes · saas-18.1
Resolved issues and error corrections
Orders in the Point of Sale preparation display no longer appear with the title "false" when a custom floating order name is unavailable. The display now falls back to the order tracking number, making kitchen or preparation workflows clearer for staff.
Original PR description
Steps to reproduce: ------------------- 1. Set up the preparation display for a PoS shop. 2. Open that PoS shop, and make an order. 3. Open the Preparation Display. -> Observed behavior: The order is shown in the preparation display, however, with a title of "false". The reason: ----------- Commit 79948eb8d38c765b2fd8703812ed9da94c197 used `floating_order_name` as the order title for the order card on the preparation display gant view. However, `floating_order_name` is not always defined, like for the case described in the reproduction steps above etc. The fix: -------- We fallback to `tracking_number` as the title of the order card, as it was the case before 79948eb8d38c765b2fd8703812ed9da94c197. opw-4597248
This update fixes errors in internal subscription sales tests that were causing build failures. It helps ensure subscription invoicing checks run reliably, reducing the risk of release delays from broken automated tests.
Original PR description
This commit address keyerror `default_pricelist` which is already defined in superclass but not used in the test case. and This commit fixes a `Field error` in the `test_postpaid_next_invoice_date` test case in the `sale_subscription` module. The error was caused by referencing an invalid field name (`tax_id`) on the `sale.order.line` model during the creation of a sale order. The correct field name, `tax_ids`, has been used instead. build_error-181599
This fixes the model creation setup so the company-specific record option appears only when multiple companies are enabled. It prevents confusion for single-company users while restoring the needed configuration for businesses operating across several companies.
Original PR description
Following 002df5f10d2378bab139ea5d59af7be3d6b40358 which made an error. When creating a new model, the feature that make a record specific to a company (ie: "use_company" -- just adds a field "company_id" on a model) should not be available when in single company mode, but should be available when in multicompany mode opw-4752832