Daily updates from Odoo
Navigate
Branch
Monday, February 21, 2022
12 changes
Enhancements to existing features
Invoice extraction now uses the proper partner autocomplete service instead of calling it directly. This avoids relying on functionality that may not be installed, making invoice processing more robust across different setups.
Original PR description
…alled Partner autocomplete was called directly instead of using the API of the dedicated module.
Resolved issues and error corrections
This fixes an issue where some country-specific reporting, e-invoicing, and check printing add-ons did not install automatically when they should have. Businesses using localized accounting setups should see required compliance features enabled more reliably without manual intervention.
Original PR description
Some modules are set to be auto installed, but with dependencies preventing the desired flow. For instance, `account_lu_reports` depends on `account_saft`, but as we don't want that module to be auto installed, `account_lu_reports` wasn't either. To fix that, we declare the module as `auto_install`ed based on the main `l10n_**` modules and the base `account_*` modules only. It is done even when not stricly necessary to give a guideline, as it was an issue for several modules not correctly auto-installed.
Documentation links across several Odoo Enterprise apps have been updated to point to the master documentation instead of older targets. This helps users and administrators reach the most current guidance when configuring features or seeking help.
Original PR description
See also: - https://github.com/odoo/odoo/pull/84990 Forward-Port-Of: odoo/enterprise#24556 Forward-Port-Of: odoo/enterprise#24271
Code cleanup and technical improvements
The spreadsheet document bundle now uses a newer shared way to handle filter rules across list and pivot features. This simplifies the underlying code and reduces reliance on outdated logic, helping future maintenance without changing expected user behavior.
Original PR description
Since Wowl, a new Domain class has been introduced which allows the manipulation of domains expressed as strings or Arrays alike and handles their combinations. Switching to this new class makes the code more straightforward and easy to read as we don't have to manually cast everything in order to use pyUtils. It also removes code that is now considered legacy. Task 2762204
Miscellaneous changes
The formula explained in a message for one of the tax report control does not match with the formula used in the actual control. Forward-Port-Of: odoo/enterprise#24568 Forward-Port-Of: odoo/enterprise#24482
Original PR description
The formula explained in a message for one of the tax report control does not match with the formula used in the actual control. Forward-Port-Of: odoo/enterprise#24568 Forward-Port-Of: odoo/enterprise#24482
Forward-Port-Of: odoo/enterprise#24523
Original PR description
Forward-Port-Of: odoo/enterprise#24523
Forward-Port-Of: odoo/enterprise#24538
Original PR description
Forward-Port-Of: odoo/enterprise#24538
Steps to reproduce the bug: - Install `point_of_sale` and `l10n_in_hr_payroll` - Connect as Admin with an Indian company - Go to POS app > shop > settings > Enable `Authorized Employees` option - Create a new user and give him: - “User” access to POS - No access to HR - Connect with the new user - Try to open a new POS session Problem: An error is triggered, because when the user does not have HR access rights, we read the `hr.employee` fields from the `hr.employee.public` m
Original PR description
Steps to reproduce the bug:
- Install `point_of_sale` and `l10n_in_hr_payroll`
- Connect as Admin with an Indian company
- Go to POS app > shop > settings > Enable `Authorized Employees` option
- Create a new user and give him:
- “User” access to POS
- No access to HR
- Connect with the new user
- Try to open a new POS session
Problem:
An error is triggered, because when the user does not have HR access rights, we read the `hr.employee` fields from the `hr.employee.public` model, while some fields are specific to `hr.employee`, as the case for the field `uan`: https://github.com/odoo/enterprise/blob/15.0/l10n_in_hr_payroll/models/hr_employee.py#L10
Solution:
Protect the fields by adding user group check
opw-[2760303](https://www.odoo.com/web#id=2760303&view_type=form&model=project.task)
Forward-Port-Of: odoo/enterprise#24426Purpose is to add performance tests for appointment module in order to be able to quantify improvements of incoming code cleaning. Tests are added currently with working hours check, on both type: either with a list of employees (type custom) or with a fixed employee (type work_hours). When forward porting to master it will be interesting to check effect of work hours on overall computation and performances as it has been split from base appointment in 15.2+ . Counters show we have so
Original PR description
Purpose is to add performance tests for appointment module in order to be able to quantify improvements of incoming code cleaning. Tests are added currently with working hours check, on both type: either with a list of employees (type custom) or with a fixed employee (type work_hours). When forward porting to master it will be interesting to check effect of work hours on overall computation and performances as it has been split from base appointment in 15.2+ . Counters show we have some room for improvements to say the least. This merge also contains * a reordering of current tests (and split of UI related tests); * addition of optional parameter to control the start of slots generation; * a fix link to appointment type creation; See sub commits for more details. Task-2766574 (Appointment: improve performance) Task-2631088 (Appointment: profile and add performance tests) Forward-Port-Of: odoo/enterprise#24501 Forward-Port-Of: odoo/enterprise#24474
2 new services appear, and one will be removed, but in the meantime, leaving it should be ok. Message from FedEx: ```Dear Valued customer, You are on the latest version of FedEx Web Services (version 26 and above), so you only need to complete two steps to be able to access our new express services FedEx International Priority® and FedEx International Priority® Express which are available from 3rd January 2022 onwards. Step 1 To enable the new services, simply enter the following val
Original PR description
2 new services appear, and one will be removed, but in the meantime, leaving it should be ok. Message from FedEx: ```Dear Valued customer, You are on the latest version of FedEx Web Services (version 26 and above), so you only need to complete two steps to be able to access our new express services FedEx International Priority® and FedEx International Priority® Express which are available from 3rd January 2022 onwards. Step 1 To enable the new services, simply enter the following values into the <ServiceType> element of your Web Services request: FEDEX_INTERNATIONAL_PRIORITY FEDEX_INTERNATIONAL_PRIORITY_EXPRESS Step 2 You should at the same time remove the existing <ServiceType> INTERNATIONAL_PRIORITY as this will be retired. ``` task-2765659 Forward-Port-Of: odoo/enterprise#24470
Steps to reproduce the bug: - Install mrp, quality and studio - Create two MO with “Table” product > validate the work order - you should have at least one WO with a test_type “register_byproducts” or “register_consumed_materials” - Go to Manufacturing > Operations > Work Orders - Edit the list view with Studio and add the `(component_remaining_qty)` field. Problem: A traceback is triggered because “self" will return multiple records Solution: We have to use “WO” inside the loop to
Original PR description
Steps to reproduce the bug: - Install mrp, quality and studio - Create two MO with “Table” product > validate the work order - you should have at least one WO with a test_type “register_byproducts” or “register_consumed_materials” - Go to Manufacturing > Operations > Work Orders - Edit the list view with Studio and add the `(component_remaining_qty)` field. Problem: A traceback is triggered because “self" will return multiple records Solution: We have to use “WO” inside the loop to refer to one WO at a time opw-2752384 Forward-Port-Of: odoo/enterprise#24506
Use case: Two lines as such: -27, using 22 in its formula and carrying over to 22 of the next period this carryover is not marked as persistent. -22 linked to a tax Let's say, using an annual periodicity In 2020, we put 100$ in 22. 27 balance would be 100. Post the closing entry. In 2021, we find 100$ in 22 again (carried over) and the same amount in 27. Post the closing entry. In 2022, the amount is now 0. This happens because we check the difference between the current and p
Original PR description
Use case: Two lines as such: -27, using 22 in its formula and carrying over to 22 of the next period this carryover is not marked as persistent. -22 linked to a tax Let's say, using an annual…
Use case: Two lines as such: -27, using 22 in its formula and carrying over to 22 of the next period this carryover is not marked as persistent. -22 linked to a tax Let's say, using an annual periodicity In 2020, we put 100$ in 22. 27 balance would be 100. Post the closing entry. In 2021, we find 100$ in 22 again (carried over) and the same amount in 27. Post the closing entry. In 2022, the amount is now 0. This happens because we check the difference between the current and past carryover, which is 0 and then reset the carryover because it is 0. But this doesn't make sense, because: - If the difference is 0, it means we have something to carryover just that it's the same amount as the last period, and so we do nothing. - If we don't carryover anything, the line amount would be 0, and thus the difference would already be -carryover_balance. There is also an issue with the Italian carryover, line vp14b. Use case: - Month 1, have a value of 25 in this line => will trigger a carryover to line vp7 - Month 2, add more value to vp14b so that it goes above 25.82. This will set the bound as None, and thus this will not impact the carryover. This is wrong, because then the next month we will see a value of 25 in vp7 while it should be 0. Forward-Port-Of: odoo/enterprise#24270