Monday, December 14, 2020
10 changes
Resolved issues and error corrections
This fixes an issue that prevented users from printing quality worksheets because the system referenced the wrong report module name. Quality teams can now generate the expected worksheet reports without manual workarounds.
Original PR description
Unable to print for quality worksheet due to the wrong module name in the report modle name.
Miscellaneous changes
Issue - Install 'stock_enterprise' module - Create a second a company - Create an inventory transfer in the first company - Switch to second company - Go to 'Inventoy -> Reporting -> Warehouse Analysis' Displayed data are from all companies. Cause No ir.rule for 'stock.report' model to filter depending current user company (or companies if multiple selected). Solution Add multi-company rule on 'stock.report' model opw-2413382 Forward-Port-Of: odoo/enterprise#1
Original PR description
Issue - Install 'stock_enterprise' module - Create a second a company - Create an inventory transfer in the first company - Switch to second company - Go to 'Inventoy -> Reporting -> Warehouse Analysis' Displayed data are from all companies. Cause No ir.rule for 'stock.report' model to filter depending current user company (or companies if multiple selected). Solution Add multi-company rule on 'stock.report' model opw-2413382 Forward-Port-Of: odoo/enterprise#15275
When using the "back" button in the event barcode scanner, when coming from the "Registration Desk" menu, the user will be redirected to the event app but the whole top menu disappears. It makes it difficult to find your way into the other apps as you are "stuck" on this view. This commit fixes that behavior using a workaround that defines an entire new action from scratch instead of using an existing one, because it seems not correctly supported by the web client. Task 2380205 Forw
Original PR description
When using the "back" button in the event barcode scanner, when coming from the "Registration Desk" menu, the user will be redirected to the event app but the whole top menu disappears. It makes it difficult to find your way into the other apps as you are "stuck" on this view. This commit fixes that behavior using a workaround that defines an entire new action from scratch instead of using an existing one, because it seems not correctly supported by the web client. Task 2380205 Forward-Port-Of: odoo/enterprise#14908
Step to reproduce: 1. Install module "sale_project" 2. In Project > Configuration > Settings, turn on "Recurring Tasks" 3. Create a recurrent task 4. Set the "next_recurrence_date" for the recurrence ahead of today 5. Run scheduled action " Project: Create Recurring Tasks" => error: 'project.task' object has no attribute 'is_fsm' Reason: "is_fsm" is used in "sale_project" module, but is defined in the "industry_fsm" module and "sale_project" module does not depend on that module. o
Original PR description
Step to reproduce: 1. Install module "sale_project" 2. In Project > Configuration > Settings, turn on "Recurring Tasks" 3. Create a recurrent task 4. Set the "next_recurrence_date" for the recurrence ahead of today 5. Run scheduled action " Project: Create Recurring Tasks" => error: 'project.task' object has no attribute 'is_fsm' Reason: "is_fsm" is used in "sale_project" module, but is defined in the "industry_fsm" module and "sale_project" module does not depend on that module. opw-2412370 Enterprise part of https://github.com/odoo/odoo/pull/63027 Forward-Port-Of: odoo/enterprise#15272
This fixes an override for updating external ids that refer to deleted records. See the corresponding fix in the `odoo` repository. OPW 2409649 See https://github.com/odoo/odoo/pull/63077 Forward-Port-Of: odoo/enterprise#15202
Original PR description
This fixes an override for updating external ids that refer to deleted records. See the corresponding fix in the `odoo` repository. OPW 2409649 See https://github.com/odoo/odoo/pull/63077 Forward-Port-Of: odoo/enterprise#15202
Spreadsheet contributors are automatically added when a spreadsheet document is modified by a user. However, merely modifying metadata (e.g. moving the document in a different workspace) should not be considered a contribution. Restrict the "contributor" detection to cases where the `raw` field is being written (i.e. the spreadsheet is saved) Forward-Port-Of: odoo/enterprise#15243
Original PR description
Spreadsheet contributors are automatically added when a spreadsheet document is modified by a user. However, merely modifying metadata (e.g. moving the document in a different workspace) should not be considered a contribution. Restrict the "contributor" detection to cases where the `raw` field is being written (i.e. the spreadsheet is saved) Forward-Port-Of: odoo/enterprise#15243
…cial bridge Currently, some issues exist if you try to create event tracks when not having social groups if push notifications are enabled in the settings. To avoid this, we now display the push reminder field all the time on the event.track form view and allow event users to enable/disable it freely. Subsequent social models search/create/write are sudo'ed to avoid ACL issues. However, you still need to have necessary social groups to be able to manually edit the push reminder ass
Original PR description
…cial bridge Currently, some issues exist if you try to create event tracks when not having social groups if push notifications are enabled in the settings. To avoid this, we now display the push reminder field all the time on the event.track form view and allow event users to enable/disable it freely. Subsequent social models search/create/write are sudo'ed to avoid ACL issues. However, you still need to have necessary social groups to be able to manually edit the push reminder associated to the track. This means that the flow of creating/updating tracks for event users should be eased and subsequent modifications will be reflected to the created event tracks. A security test was added to ensure this behavior. Task 2382683 Forward-Port-Of: odoo/enterprise#15257 Forward-Port-Of: odoo/enterprise#15027
The method used to retrieve the possible spreadsheets for inserting a pivot table was not working for non-admin users. Steps to reproduce the error: create some spreadsheets with an admin user in a workspace that is not accessible to normal users, then with a normal user try to use the "INSERT IN SPREADSHEET" button on a pivot view -> Access Error. Documents/Spreadsheet have specific access rules, and the filters are (expected to be) consistently implemented in CRUD methods. Using
Original PR description
The method used to retrieve the possible spreadsheets for inserting a pivot table was not working for non-admin users.
Steps to reproduce the error: create some spreadsheets with an admin user in a workspace that is not accessible to normal users, then with a normal user try to use the "INSERT IN SPREADSHEET" button on a pivot view -> Access Error.
Documents/Spreadsheet have specific access rules, and the filters are (expected to be) consistently implemented in CRUD methods. Using direct SQL to retrieve all spreadsheet "candidates" then manually calling `check_access()` on the list is bound to cause access errors for all those that are unavailable to the current user.
Fix it by using the proper CRUD methods to obtain the list of available spreadsheets for the user. The code is also simpler.
Forward-Port-Of: odoo/enterprise#15242PURPOSE Provide various fixes related to mass mailing (sms) and marketing automation applications. SPECIFICATIONS See sub commits for more details. [FIX] marketing_automation(_sms): remove creation option from reporting stat buttons [FIX] marketing_automation: do not display MA mailings in standard mailing reporting LINKS Task ID-2300385 COM PR odoo/odoo#59872 ENT PR odoo/enterprise#14031 Forward-Port-Of: odoo/enterprise#14031
Original PR description
PURPOSE Provide various fixes related to mass mailing (sms) and marketing automation applications. SPECIFICATIONS See sub commits for more details. [FIX] marketing_automation(_sms): remove creation option from reporting stat buttons [FIX] marketing_automation: do not display MA mailings in standard mailing reporting LINKS Task ID-2300385 COM PR odoo/odoo#59872 ENT PR odoo/enterprise#14031 Forward-Port-Of: odoo/enterprise#14031
In Mexican localization, landed costs have an extra field, l10n_mx_edi_customs_number, that has a sql unique constraint. Before this commit, the customs number was unique in the database. It exists two different scenarios in which this could cause an issue : - A shipment could be split through several of the companies using the same customs number; - A customer is "migrating" all of their information from one of the companies in the database to another. In both cases, the c
Original PR description
In Mexican localization, landed costs have an extra field,
l10n_mx_edi_customs_number, that has a sql unique constraint.
Before this commit, the customs number was unique in the database. It
exists two different scenarios in which this could cause an issue :
- A shipment could be split through several of the companies using the
same customs number;
- A customer is "migrating" all of their information from one of the
companies in the database to another.
In both cases, the customs numbers can only be used in first company.
Now, the customs number is unique by company in the database.
opw-2390654
Forward-Port-Of: odoo/enterprise#15225
Forward-Port-Of: odoo/enterprise#15220