Wednesday, April 9, 2025
9 changes · saas-18.1
Resolved issues and error corrections
The unit of measure tag widget now avoids blocking errors when older database views still contain outdated settings. Instead of crashing, it logs a warning and falls back to a safe default, helping users continue working until views are refreshed.
Original PR description
In 8ce6e7a426834210dc861b5f92d216a86062dc2e an error is thrown if the `many2many_uom_tags` is not correctly configured. Following that, some uses of this widget were removed (see 51c4e461eb13b01f6c752171c25214d5b612a443 for example) but the issue is, for DB with unreloaded view, the wrong uses of widget will still be in the templates alongside with the code throwing an error is triggered. To avoid that, this commit replaces the thrown error by a warning in the console and will use `product.product` as the model if those cases (which can also causes a traceback since it was the initial error.)
Point of Sale orders created while offline now receive the expected default reference value. This avoids log errors when restaurant staff reconnect and reload or update orders on the same table, making offline order handling more reliable.
Original PR description
Currently, an exception is generated in the log when the users create a POS order as follows - Install module pos_restaurant. - Open `POS Restaurant`. - Add some products to the order go to…
Currently, an exception is generated in the log when the users create a POS order as follows - Install module pos_restaurant. - Open `POS Restaurant`. - Add some products to the order go to `Payments`, and select card(Pick any table) - Open Inspect, go to the Network tab and enable Offline Mode. - Click Validate, go to Orders, and click Load Order. - Add Products to the Orders and click on Order. - In the Network tab, enable No Throttling and click on Orders again. - Do the above step one more time `on the same table`. This error occurs when the system tries to fetch the order reference name in offline mode, it receives False instead of the default value '/', because the name field is initialized in Python at [1] as fields.Char(default='/'). To resolve this, the commit initializes the `name` on the server side to ensure it defaults to "/". Ref: https://github.com/odoo/odoo/pull/202525 Link [1]: https://github.com/odoo/odoo/blob/2aa8c180b33ed17d35b8fadc3ef4ad267e6c523d/addons/point_of_sale/models/pos_order.py#L254 Sentry - 6365371665 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Restaurant point of sale orders sent to preparation tools now avoid being synchronized twice in quick succession. This reduces unnecessary processing and helps prevent duplicate updates when staff send an order from a table.
Original PR description
When the order is sent to the preparation tools, synchronization is performed twice. This is because synchronization is done in the preparation tool method and in the unsetTable method. Add last synchronization date to order states. If it has been synchronized within 2 seconds, the second call is not made. taskId: 4664549
This fixes an internal point of sale test by using dedicated test data instead of optional demo data. It helps keep automated quality checks stable, reducing false failures during release validation.
Original PR description
Change used category in test from `Chairs` which is demo data to `Chair Test` runbot error: 162925, 162923
The New Zealand localization now reports GST-only import tax amounts in the correct IRD GST return box. This helps businesses avoid misclassifying imported goods GST in their tax reporting.
Original PR description
Current set up under the tax concerned is "BOX 11" which is incorrect as according to the IRD GST report, BOX 11 excludes the amount of imported goods. The tax in consideration is used when the NZ Customs bills the user only for the GST amount based on the purchase value of the goods. Therefore, the tax grids for this tax need to changed to "BOX 13". Backport of 6d70452299cb06ad65bb745218fedfcbdb8f2c8e PR backport: https://github.com/odoo/odoo/pull/202382 task-3926151
The comment composer no longer shows a file upload action that was not relevant and did not work in that context. This avoids user confusion and keeps the comment workflow focused on supported actions.
Original PR description
The upload file action is available in the comment composer, but it's not relevant to what this composer is expected to do, and it doesn't work there. This PR removes that action from the comment composer. part of task-4712487
This fix ensures vendor price list entries created through purchase approvals include the correct unit of measure. This helps prevent purchasing mistakes or inconsistent supplier pricing when converting approved requests into purchase data.
This fix stops restaurant preparation orders from being synchronized twice when they are sent to preparation tools. It helps avoid duplicate processing work and keeps order status updates cleaner and more reliable for staff.
Original PR description
When the order is sent to the preparation tools, synchronization is performed twice. This is because synchronization is done in the preparation tool method and in the unsetTable method. taskId: 4664549
Orders sent from retail shops to the preparation display now show a meaningful card name instead of “false”. Retail orders display the tracking number with the POS reference, while restaurant orders keep the appropriate name, direct sale label, or table number.
Original PR description
If an order is send to the preparation display from a retail shop `false` was shown as card name. This was because `floating_order_name` is not used in retail shops. New behavior from retail shop: - Order card name is `tracking_number (pos_reference)` New behavior from restaurant: - Order card name is `floating_order_name` or `Direct Sale` or `table_number`. taskId: 4711882