Daily updates from Odoo
Friday, February 7, 2025
7 changes
1 change
Resolved issues and error corrections
Starting a manufacturing order from the shop floor no longer automatically consumes components that were set for manual consumption. This helps keep production records accurate and ensures teams control manually managed materials as intended.
Original PR description
With this Commit : ---------------------------------------------------------- - In the previous implementation, components marked for manual consumption were automatically consumed, like auto-consumed components, when starting production on a manufacturing order (MO). This occurred due to missing logic and conditions in the code that failed to differentiate between manual and automatic component consumption, and it only affected the shop floor operations. - This update corrects the components' consumption process and enhances production tracking's reliability, ensuring that manual components are managed according to their intended usage. Task id: 4096514 Enterprise PR: odoo/enterprise#77831
2 changes
Resolved issues and error corrections
Companies can now view and update the rental location used for rental order replenishment. This prevents users from being blocked after a rental location is deleted, and also restores missing rental locations automatically during setup.
Original PR description
### Problem Before this commit, if the customer deletes the rental location they would be blocked from creating a rental order as it is necessary for replenishment rules. The issue becomes critical because, once deleted, the rental location cannot be set to the company functionally given the field is not present in the view. ### Solution To fix this, this commit adds `Rental Settings` making the `rental_loc_id` field visible in the `res_company` view, allowing customers to select their desired rental location and resolve the issue independently. Additionally, we call `create_missing_rental_location()` in the `post_init_hook` to ensure that the field is correctly set for all companies.  - opw-3973957 - opw-4488182 - opw-4545985
This update fixes how units of measure are handled when orders are created from replenishment and improves how conversion ratios are shown against a product's base unit. This helps users avoid quantity mistakes and better understand unit conversions in purchasing approval and quality control flows.
4 changes
Resolved issues and error corrections
This fix restores behavior that prevents imported accounting lines from unexpectedly changing tax values. It helps businesses avoid incorrect tax handling when importing accounting data, reducing manual corrections and compliance risk.
Original PR description
[IMP] account - imported line shouldn't change tax Foward-port https://github.com/odoo/odoo/pull/193483 messed up and removed important code of https://github.com/odoo/odoo/pull/172787. This commit adds it back. task-4547597 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Point of Sale order screen now handles offline and slow connections more gracefully. Staff can continue viewing previously loaded orders instead of seeing a blank screen or getting stuck in repeated loading.
Original PR description
This fix prevent blank screen (when offline) & inifinte loop (when in 3G or other low connection) on order screen. - **Offline Mode:** When accessing the order screen offline, now the screen loads previously fetched orders and displays a "Limited Functionality" popup. - **Slow Connection (3G):** Infinite loop (caused by repeated call to `await this.pos.getServerOrders()`) is fixed by ensuring orders load only once, even on slow connections using the flag `loadingOrderState` task-id: 4550978 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Selecting multiple documents with Shift now works correctly in both kanban and list views. This prevents folders from being accidentally selected and aligns document list behavior with other Odoo list views, making bulk actions more reliable.
Original PR description
Before this commit, In kanban view when selecting multiple documents while holding shift as modifier, it could happen that folders were selected too. This was due to the logic which was using document ids as the range value when looping on `root.records` but with the new UI where the folders are now displayed on top of the documents it was buggy. In list view, we would like to keep the same behavior as in other list views. This commit fixes those issues. Task-4532046
Users can now reliably insert views or view links from custom menus into Knowledge articles. This prevents failed insertions and error pages when navigating from custom menu actions, helping teams keep article content connected to the right business views.
Original PR description
Issue ===== The view is not inserted into the article, or the view link results in a traceback error. Steps ====== 1. Create a custom menu with its configuration using the model (Create a Menu). 2. Navigate to the custom menu action via the parent menu's route. 3. Use the actions to navigate to Knowledge > Insert view/link in article, then select an article (either existing or new). Technical ========= Due to a recent change introduced in this [commit](https://github.com/odoo/enterprise/commit/30c71b1fee8c91df5342b2b1ef5f6e888e84571d) the issue arises from the function 'this.actionService.loadAction' requiring either an actionxmlid or actWindow to process the action. Previously, only the actionxmlid was available, which caused the problem. The provided fix resolves this issue by ensuring both identifiers are correctly handled. Task-4437944