Thursday, April 20, 2023
5 changes · master
Resolved issues and error corrections
This fixes an issue where selecting fields such as Sales Team on mobile could show the wrong list view in newer Odoo versions. The change updates how related kanban views are referenced so users see the intended selection interface across Sales, CRM, POS Sales, and website sales flows.
Original PR description
Steps to reproduce: - Install Sales. - Go to any quotation and toggle mobile device mode in the browser. - Go to Other Info > click in Sales Team field. Issue: We stop supporting the 'kanban_view_ref' in newer versions of odoo. So we won't be able to get proper view. Solution: Changed the way we ref the kanban view to use context to get the referenced kanban view. Related to #[39499](https://github.com/odoo/enterprise/pull/39499) opw-3152174
Manufacturing orders for serial-tracked products can now be completed correctly after using Mass Produce. This prevents an error that blocked users from validating split production orders, helping production teams finish batches without manual workarounds.
Original PR description
Description of the issue/feature this PR addresses: Issue : When mass producing a tracked product, an User Error is raised on validation of splitted MO. Reproduction : - Create Serial storable product "Component A", Lot storable product "Component B", Serial Storable product "Finished Serial Product" - Immediate Transfer 10 * "Component A" and 20 * "Component B" - Create a BoM for "Finished Serial Product", consuming 1 * "Component A" and 2 * "Component B" - Create a Manufacturing Order for 10 * "Finished Serial Product" and Confirm - Click on "Mass Produce", Set "First SN", Generate all the serials and Apply - Click on "Produce All" on the splitted MO Current behavior before PR: User Error Desired behavior after PR is merged: Working fine Task : 3274962 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
A recent internal refactoring accidentally removed handling for simple notification alerts used by several Odoo apps. This fix restores those alerts so users continue to see important messages with the expected warning or danger level.
Original PR description
* = base_geolocalize, calendar, website_crm_partner_assign Oversight of discuss refactoring. Code is restored into bus module as it does not depend on any mail or discuss feature. ----- Note: default type (unless `warning` was specified) was `danger` before https://github.com/odoo/odoo/blob/5da763a8ef0503286fa5cc55e32970f4d785825a/addons/mail/static/src/models/messaging_notification_handler.js#L429 and now the default from notification service is kept (it is `warning`) so `danger` is added in code to keep the same behavior.
Odoo Studio now correctly ignores fields that a user is not allowed to access when opening or editing views. This prevents access rights errors and lets users continue working in Studio even when a view contains restricted fields.
Original PR description
Commit @baebb6a5b05ac8d59501a6071a5513e31a4ca047 introduced a universal way to handle multiple instances of the same field in a view arch. To do so, it separates what fields are to be fetched (activeFields) from the "instances" of those fields in the arch (fieldNodes). Studio's code was only partially ready, relying on the fact that the key for fieldNode was the field's name, which isn't true any longer. This commit fixes that, and removes from the fieldNodes the ones that have studio_no_fetch and more importantly removes them from activeFields. To reproduce: have a field with a group declared in python, which the user doesn't have. Open studio with a view that has that field in the arch. Before this commit, there was an access rights crash. After this commit, there is no crash.
Users can now insert links to Odoo menus in spreadsheets without being unexpectedly sent back to the Odoo home page. The menu picker also better reflects the currently selected item and includes apps, making accidentally removed app links easier to restore.
Original PR description
This PR fixes the problem when inserting a link to an odoo menu, clicking the menu item in the dropdown will jump to odoo home page, and the insertion fails. The root cause is the menu item uses `a` tag and has a `href` leading to home page. The solution is to prevent the default clicking behavior. This PR also fixs a small bug of showing currently selected menu item. task [3159543](https://www.odoo.com/web#id=3159543&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form)