Thursday, July 2, 2020
31 changes · master
Enhancements to existing features
The account list view now includes each account's group, making it easier for users to understand and organize accounts at a glance. This small usability improvement helps accounting teams review account structures more efficiently without opening individual records.
Original PR description
as per requested on #52948
This update adds broader automated checks for electronic invoicing, including Factur-X documents. It helps reduce the risk of invoice generation or exchange issues reaching customers by catching problems earlier during development.
Original PR description
…rx tests -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Improves the wording and translation support for messages shown when users edit system views. This helps users see clearer localized error messages while keeping internal warning logs unchanged.
Original PR description
* Translate all error messages (raised to the User modifying an `ir.ui.view`) * Do not translate warnings (not shown to the user, only logged) * Use the new _ signature (https://github.com/odoo/odoo/pull/52155) * Fix some typos. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update keeps server log messages in a consistent language instead of translating them for individual users. This makes troubleshooting easier for support and operations teams because logs are clearer and more uniform across systems.
Original PR description
-- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update keeps server log messages in a single language instead of translating them based on user or system settings. It makes troubleshooting easier for support and operations teams because logs remain consistent across modules and environments.
Original PR description
The logs should all be in the same language, s.t. one does not need to understand multiple languages when browsing/reading the server logs. Enterprise counterpart of https://github.com/odoo/odoo/pull/53984
Resolved issues and error corrections
This update fixes an internal test so it works correctly after installation. It helps maintain product quality by ensuring automated checks run reliably without affecting day-to-day users.
Miscellaneous changes
This pull request appears to make minor maintenance updates across accounting, sales, point of sale, and localization areas, mostly affecting tests and payment-related logic. The sparse description and commit message make the business impact unclear, but the scope suggests low-risk validation or compatibility improvements rather than a major user-facing change.
Original PR description
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
Write is overridden on reserved move lines to make sure the quants are correctly updated. It is divided in two parts: if you update the reserved quantity and if you update a characteristic. If somehow both are updated in the same call (which doesn't happen in the standard interface), then the quants are unreserved two times, which is wrong. This issue showcased by [0] and on databases where the reserved quantities are made editable by customization. We grouped the two update in one, s
Original PR description
Write is overridden on reserved move lines to make sure the quants are correctly updated. It is divided in two parts: if you update the reserved quantity and if you update a characteristic. If somehow both are updated in the same call (which doesn't happen in the standard interface), then the quants are unreserved two times, which is wrong. This issue showcased by [0] and on databases where the reserved quantities are made editable by customization. We grouped the two update in one, such as the TODO indicated us since a long, long time. We removed `result_packaged_id` from the trigger because it should not impact the reservation whatsoever. We needed to remove a tricky logic in the stock move's backordering part but it was fishy anyway. [0] eac8c06e2233 Forward-Port-Of: odoo/odoo#53794
- Create an invoice with a Product X and Post it; - Generate a Credit Note from the invoice; - Reporting > Invoices; - use Pivot Table View; - Enable 'Product Quantity' in Measures; - Filter by 'Invoice #'; - Expand Pivot Table by 'Product'. Before this commit, the products in the credit note had a positive sign, contrary to the untax total that has a negative sign. The issue with this, is when the quantities of the credit notes is added with the quantities of the invoices the total
Original PR description
- Create an invoice with a Product X and Post it; - Generate a Credit Note from the invoice; - Reporting > Invoices; - use Pivot Table View; - Enable 'Product Quantity' in Measures; - Filter by 'Invoice #'; - Expand Pivot Table by 'Product'. Before this commit, the products in the credit note had a positive sign, contrary to the untax total that has a negative sign. The issue with this, is when the quantities of the credit notes is added with the quantities of the invoices the total is not coherent with the actual sell products. Now, the product quantity that comes from a credit note has a negative sign. opw-2283833 Forward-Port-Of: odoo/odoo#53877 Forward-Port-Of: odoo/odoo#53795
An id should be passed instead of a record. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#53716
Original PR description
An id should be passed instead of a record. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#53716
Adapt the position of the navbar according the height/visibility of the header (effects, logo size, preheader). task-2269822 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 Forward-Port-Of: odoo/odoo#52708
Original PR description
Adapt the position of the navbar according the height/visibility of the header (effects, logo size, preheader). task-2269822 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 Forward-Port-Of: odoo/odoo#52708
A product can't be archived if it's used in a pos loyalty program. opw-2276745 Forward-Port-Of: odoo/odoo#53868 Forward-Port-Of: odoo/odoo#53786
Original PR description
A product can't be archived if it's used in a pos loyalty program. opw-2276745 Forward-Port-Of: odoo/odoo#53868 Forward-Port-Of: odoo/odoo#53786
Before this fix, the search on the supplierinfo had an indeterministic result. When testing odoo/addons/purchase_stock/tests/test_reordering_rule.py:66 `def test_procure_not_default_partner`, it may fail at line 120. It sets 2 suppliers: - Firstly, the `default_vendor` - Then, the `secondary_vendor` It then runs a procurement without setting the supplier and asserts that the partner of the resulting PO line should be `default_vendor`. The return of `odoo/addons/product/models/pro
Original PR description
Before this fix, the search on the supplierinfo had
an indeterministic result.
When testing odoo/addons/purchase_stock/tests/test_reordering_rule.py:66
`def test_procure_not_default_partner`, it may fail at line 120.
It sets 2 suppliers:
- Firstly, the `default_vendor`
- Then, the `secondary_vendor`
It then runs a procurement without setting the supplier and asserts
that the partner of the resulting PO line should be `default_vendor`.
The return of
`odoo/addons/product/models/product.py:574`
`def _prepare_sellers` depends on Postgres when the supplierinfo
sequence, min_qty and price are the same for multiple records.
By adding the `id` to the `.sorted`, the result will order correctly in that
case.
opws-2272627
-2282081
-2287079
And PS-BE via CSC reported more cases without opw.
Forward-Port-Of: odoo/odoo#53939As the `purchase.order.line` `state` field is invisible but editable in the RFQ form, when the user will create a new line, this new line's state will be save with an empty value instead of taking the RFQ state. Forward-Port-Of: odoo/odoo#53898
Original PR description
As the `purchase.order.line` `state` field is invisible but editable in the RFQ form, when the user will create a new line, this new line's state will be save with an empty value instead of taking the RFQ state. Forward-Port-Of: odoo/odoo#53898
Some features need the time to be synchronized before starting: - A certificate might be considered valid and therefore not renewed if the time is not synced. - If the time is not correct when the pairing code is retrieved, it will disappear as soon as the time is synced because more than 5 minutes will have "passed" since the code was retrieved. We then make sure that the time is synced, or that the box is not connected to the internet (because in this case the time will never be sync
Original PR description
Some features need the time to be synchronized before starting: - A certificate might be considered valid and therefore not renewed if the time is not synced. - If the time is not correct when the pairing code is retrieved, it will disappear as soon as the time is synced because more than 5 minutes will have "passed" since the code was retrieved. We then make sure that the time is synced, or that the box is not connected to the internet (because in this case the time will never be synced and those features cannot work with a connection anyway). -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#53905
- Make sure to have 'Billing' access rights - Create an invoice - Fully paid this invoice - Try to unreconcile the newly created payment => You should have the access rights to do that -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#53659
Original PR description
- Make sure to have 'Billing' access rights - Create an invoice - Fully paid this invoice - Try to unreconcile the newly created payment => You should have the access rights to do that -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#53659
Forward-Port-Of: odoo/odoo#53530 Forward-Port-Of: odoo/odoo#53446
Original PR description
Forward-Port-Of: odoo/odoo#53530 Forward-Port-Of: odoo/odoo#53446
Update the version for the new build of IoT Box 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 Forward-Port-Of: odoo/odoo#53954
Original PR description
Update the version for the new build of IoT Box 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 Forward-Port-Of: odoo/odoo#53954
'payment_state'='sent' has been replaced by the 'is_move_sent' field. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#53865
Original PR description
'payment_state'='sent' has been replaced by the 'is_move_sent' field. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#53865
Trying to call display_refresh or update_url when no screen was connected to the IoT Box and the default distant_display was created resulted in an error. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#53968
Original PR description
Trying to call display_refresh or update_url when no screen was connected to the IoT Box and the default distant_display was created resulted in an error. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#53968
Create an invoice, fill document type "(61) Nota de Crédito Electrònica". Save. Action will be blocked by a warning: document type is invalid. Some options in the document type should not be shown as they can not be used in the customer invoices and customer credit note. opw-2286623 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#53971
Original PR description
Create an invoice, fill document type "(61) Nota de Crédito Electrònica". Save. Action will be blocked by a warning: document type is invalid. Some options in the document type should not be shown as they can not be used in the customer invoices and customer credit note. opw-2286623 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#53971
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 Forward-Port-Of: odoo/odoo#53909
Original PR description
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 Forward-Port-Of: odoo/odoo#53909
In case the COA is imported in the system, the `chart_template_id` of the company remains empty while the accounting is usable. However, in this case it's impossible to open a POS session. We leave the warning in the POS config but avoid blocking the user. opw-2286640 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
Original PR description
In case the COA is imported in the system, the `chart_template_id` of the company remains empty while the accounting is usable. However, in this case it's impossible to open a POS session. We leave the warning in the POS config but avoid blocking the user. opw-2286640 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 Forward-Port-Of: odoo/odoo#53969 Forward-Port-Of: odoo/odoo#53963
Issue - Install 'Accounting' app - Create tax A and tax B for 5%, make sure they are NOT included in price - Create a tax C as a group that includes Tax A and B - Go to any bank journal and create a statement line for 100 dlls - Click Reconcile - Select Manual Operations - Select any account - Add Tax C - Check on 'Tax Included in Price' Wrong calculation. Cause Not considering forced 'Tax Included in Price' ('force_price_include'),when accumulating tax included
Original PR description
Issue
- Install 'Accounting' app
- Create tax A and tax B for 5%, make sure they are NOT included in price
- Create a tax C as a group that includes Tax A and B
- Go to any bank journal and create a statement line for 100 dlls
- Click Reconcile
- Select Manual Operations
- Select any account
- Add Tax C
- Check on 'Tax Included in Price'
Wrong calculation.
Cause
Not considering forced 'Tax Included in Price'
('force_price_include'),when accumulating tax included
amount.
opw-2280714
Forward-Port-Of: odoo/odoo#53946
Forward-Port-Of: odoo/odoo#53871When the OCR try to applies the values to an invoice, it searches for an existing tax. This search must take the company into account, otherwise an AccessError is raised. Forward-Port-Of: odoo/enterprise#11613 Forward-Port-Of: odoo/enterprise#11578
Original PR description
When the OCR try to applies the values to an invoice, it searches for an existing tax. This search must take the company into account, otherwise an AccessError is raised. Forward-Port-Of: odoo/enterprise#11613 Forward-Port-Of: odoo/enterprise#11578
When you download only one document (pdf or xml) a multicompany issue happened. opw-2216209 Forward-Port-Of: odoo/enterprise#11600
Original PR description
When you download only one document (pdf or xml) a multicompany issue happened. opw-2216209 Forward-Port-Of: odoo/enterprise#11600
Forward-Port-Of: odoo/enterprise#11587
Original PR description
Forward-Port-Of: odoo/enterprise#11587
Before this commit, when a product was archived and that product was used in a loyalty program (as a reward or in the rules), a traceback error arise when trigger the loyalty program in the POS. opw-2276745 Forward-Port-Of: odoo/enterprise#11543 Forward-Port-Of: odoo/enterprise#11472
Original PR description
Before this commit, when a product was archived and that product was used in a loyalty program (as a reward or in the rules), a traceback error arise when trigger the loyalty program in the POS. opw-2276745 Forward-Port-Of: odoo/enterprise#11543 Forward-Port-Of: odoo/enterprise#11472
- Activate developer mode - Go to Consolidation Dashboard and Create - Set a Consolidation and an End Date - In the 'Sub-consolidations Periods' tab, try to add a line A JS error is raised. It occurs because the record is not saved yet, so `parent.id` doesn't exist. We replace the domain by a constrain. opw-2284554 Forward-Port-Of: odoo/enterprise#11576
Original PR description
- Activate developer mode - Go to Consolidation Dashboard and Create - Set a Consolidation and an End Date - In the 'Sub-consolidations Periods' tab, try to add a line A JS error is raised. It occurs because the record is not saved yet, so `parent.id` doesn't exist. We replace the domain by a constrain. opw-2284554 Forward-Port-Of: odoo/enterprise#11576
Create a purchase order Confirm Create the bill from the PO Some fields related to the partner are left empty, shipping address, incoterms, ... While the account.move related to the bill is created, no onchanges are triggered, so partner additional info are not loaded in the account move form. opw-2276391 Forward-Port-Of: odoo/enterprise#11351 Forward-Port-Of: odoo/enterprise#11294
Original PR description
Create a purchase order Confirm Create the bill from the PO Some fields related to the partner are left empty, shipping address, incoterms, ... While the account.move related to the bill is created, no onchanges are triggered, so partner additional info are not loaded in the account move form. opw-2276391 Forward-Port-Of: odoo/enterprise#11351 Forward-Port-Of: odoo/enterprise#11294
In Sales Quotation, when adding DHL as shipping method and computing rate, the following error may be triggered "AttributeError: 'NoneType' object has no attribute 'settings'". It comes from the fact that sometimes, when requesting rate from DHL API, its XML response does not respect its schema definition (XSD). Which triggers an error in zeep library. As DHL API responses do not seem to always respect its XSD, the parsing of the XML response for the rate will be done with "lxml" inste
Original PR description
In Sales Quotation, when adding DHL as shipping method and computing rate, the following error may be triggered "AttributeError: 'NoneType' object has no attribute 'settings'". It comes from the fact that sometimes, when requesting rate from DHL API, its XML response does not respect its schema definition (XSD). Which triggers an error in zeep library. As DHL API responses do not seem to always respect its XSD, the parsing of the XML response for the rate will be done with "lxml" instead of "zeep", as it was in v12. opw-2263982 Forward-Port-Of: odoo/enterprise#11571