Daily updates from Odoo
Thursday, December 12, 2019
5 changes · master
Resolved issues and error corrections
This fixes a small issue caused by a previous web client test change that accidentally removed behavior still needed by Enterprise. Restoring the startup flag helps ensure related automated tests and Enterprise web behavior continue to work as expected.
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
This update removes or adjusts unstable automated tests that could pass or fail unpredictably. It helps the development team get more trustworthy test results, reducing false alarms and improving confidence in future changes.
Original PR description
this test needs to wait to 2 nextTick (nextAnimationFrame) -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update ensures Odoo tracks check numbers in a numeric format as well as text, so the next check number is calculated correctly. Businesses paying vendor bills by check will see the proper next number instead of the widget repeatedly showing 1.
Original PR description
Go to Accounting > Vendor Bill, pay via check, view the invoice and click on 'Print Check'. The widget will popup but as the 'next check number' will always display 1. This append because the model of account_payment has changed https://github.com/odoo/odoo/blob/13.0/addons/account_check_printing/models/account_payment.py#L28 and now check_number is a char so it will not sorted correcly by the database. To avoid doing a lot of strings manipulation it is convenient to store the check number as integer, with proper default case Followup of opw 2151242 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix clarifies how pivot table header clicks are detected in the web interface. It helps maintain reliable pivot table behavior and reduces the risk of future regressions when users interact with reports.
Original PR description
This commit explains why we use isHeaderClicked. 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 a reconciliation model during manual reconciliation now works without triggering an error caused by missing currency information. This prevents interruptions for accounting users and keeps the reconciliation workflow usable.
Original PR description
Before that, an empty account.bank.statement.line recordset was passed to the function, and caused the recordset containing the currency to use to also be empty, eventually leading to a rounding value of 0, which raised and error.