Monday, October 10, 2022
6 changes · master
New functionality added to Odoo
Adds a tax calculation option that compares a percentage-based tax with a quantity-based fixed amount and applies whichever is higher. This helps businesses comply with tax rules that require minimum per-quantity tax amounts while still using percentage tax when it produces a larger value, including in Point of Sale.
Original PR description
In this commit, we add a new type that does tax calculation in fixed/percent and takes the higher one. Tax is 21% or 4170 INR per 1000 qty which is high Product | QTY | Unit Price | Total without tax…
In this commit, we add a new type that does tax calculation in fixed/percent and takes the higher one. Tax is 21% or 4170 INR per 1000 qty which is high Product | QTY | Unit Price | Total without tax | Tax amount ========|=====|============|===================|=========== A | 10 | 100.0 | 1000.0 | 417.0 B | 50 | 100.0 | 5000.0 | 1050.0 In first-line tax calculation is 21% of 1000 = 210.0 100(QTY) * 4.17 = 417.0 Tax value is 417.0 (based on qty because the value is higher than the percentage calculation) In second-line tax calculation is 21% of 5000 = 1050.0 100(QTY) * 4.17 = 417.0 Tax value is 1050.0 (based on percentage because the value is higher than qty base calculation) task-2741537 PR: #84518 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
Enhancements to existing features
Invoices now show bank statement information when a manually registered payment has been reconciled through a posted bank statement. This helps users open the right bank reconciliation view directly instead of being sent to the payment record, making follow-up and review clearer.
Original PR description
When a payment is registered manually and reconciled with a bank statement, the payment widget on the invoice still displays payment data. Clicking the "View" button also redirects to the `account.payment` form. Once a bank statement is posted, it is preferred to show the bank statement information and redirect to a bank reconciliation widget view, filtered by the bank statement line reconciled with the payment. In a very unlikely case that a payment is reconciled with more than one bank statement line, we display the last statement's data and filter the reconciliation widget by the last statement line posted. task-2928299 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
Creating a timesheet from an employee's grid view now correctly links the entry to that employee when no employee was set explicitly. This fixes a workflow issue that prevented users from adding timesheets directly after creating a new employee.
Original PR description
…work Before this commit, when create new employee and click to timesheet button that time adding a new timesheet from the grid view doesn't work. After this commit, In hr_timesheet we have use default_employee_id form context while creating timesheet record if employee_id is not present in vals, so when create new employee and adding a new timesheet from the grid view it is work. task-2973173 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
Code cleanup and technical improvements
This change updates the internal way the mail and discussion features store and refresh message-related data. It is intended to make the interface more reliable and responsive without changing the visible workflow for users.
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
Companies can now be archived when they are no longer in use, such as after closing a subsidiary, without needing to delete historical business records. This keeps past invoices, payments, and related data intact while removing inactive companies from everyday use.
Original PR description
It is technically nearly impossible to delete a company when it actually dealed with customers (emitted invoices, received payments, ...). Hence, if you want to get rid of a company, for instance because you closed one of your subsidiaries, giving the possibility to archive your company, thanks to an active field, would be the best way to go. We are hesitating to do a related field to the `partner_id.active`, but we are a bit afraid some people archive the partner linked to their company for other valid reasons than get rid of their subsidiary (such as avoid changing the address of their company by mistake through the Contacts app), while still wanting the company itself to be active. So, we make it an independant column at the moment, so we have the actual stored column in case we need it, and will do a related stored to the partner later on if we change our mind. *edit*: manual forward-port of https://github.com/odoo/odoo/pull/102801
The spreadsheet component was updated to make common actions smoother and more reliable. Users can now adjust filters in read-only mode where allowed, clear cell contents with Backspace, and benefit from an internal safeguard that prevents duplicate data access names.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/1af8ad34 [IMP] filters: allow to update a filter in readonly mode https://github.com/odoo/o-spreadsheet/commit/706cc8ee [FIX] model: ensure that two getters cannot have the same name https://github.com/odoo/o-spreadsheet/commit/96067749 [IMP] grid: allow to remove content of a cell with backspace