Wednesday, April 16, 2025
3 changes · saas-18.1
Resolved issues and error corrections
Opening a field service task from the activity view no longer triggers an error on large screens. The fix ensures the window-opening option is always initialized, so users can access task forms without interruption.
Original PR description
Steps to Reproduce: - Open the industry fsm app and navigate to the activity view. - Click on any task to open its form view. Issue: - A traceback error occurs when opening a task on large screens because 'newWindow' is undefined. Fix: - Set a default empty objec in openRecord to ensure 'newWindow' is always defined. [Issue](https://github.com/odoo/enterprise/commit/2bd4b62d828cc0a283bcbf12eccd918c2d8076b6) task-4664793
This fix prevents an error when creating vendor pricelists without a unit of measure. Users can continue replenishment workflows without the system crashing in this edge case.
Original PR description
Ensure product_uom_id is set before calling _compute_price to avoid a singleton constraint error. The issue occurs when product_uom_id is not assigned on newly created vendor pricelists, leading to…
Ensure product_uom_id is set before calling _compute_price to avoid a singleton constraint error. The issue occurs when product_uom_id is not assigned on newly created vendor pricelists, leading to ensure_one() failing. This fix safeguards against the issue by adding a conditional check before computing the price. Exact steps list to reproduce the issue happens when product_uom_id is not set on all new vendor pricelists so it throws an error due to ensure_one() being called : 1- Go to Inventory → Operations → Replenishment 2- Create a new vendor pricelist without setting product_uom_id 3- Error occurs due to ensure_one() being called on an empty recordset another linked PR that ensures product_uom_id is set on all new vendor pricelists : #203751 Traceback (most recent call last): File "/home/odoo/src/odoo/saas-18.1/odoo/orm/models.py", line 6107, in ensure_one _id, = self._ids ^^^^ ValueError: not enough values to unpack (expected 1, got 0) opw-4665300 (related to ticket)
Opening a field service task from the Activity view now works reliably on large screens. This prevents an error that could interrupt dispatchers or field service users when accessing task details.
Original PR description
Steps to Reproduce: - Open the Industry FSM app and navigate to the Activity view. - Click on any task to open its form view. Issue: - A traceback error occurs when opening a task on large screens due to 'newWindow' being undefined. Solution: - Passed the 'options' argument to super.openRecord in FsmMyTaskActivityController to ensure 'newWindow' is defined on large screens. - Ensured consistent behavior for openRecord across devices. task-4664793