Daily updates from Odoo
Monday, November 25, 2019
21 changes
New functionality added to Odoo
Mobile users can now add a new Kanban column directly from a dedicated “Add Column” tab. This makes board management easier on phones and keeps users in the right place after creating or cancelling a column.
Original PR description
Task: https://www.odoo.com/web?debug=1#id=1893137&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.39bed8937b446b5c076185288f5f6e1b -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Sales users can now enable a product grid configurator to choose multiple product variants in a single flow. This helps teams handle products with many variants more efficiently and reduces repetitive order entry work.
Original PR description
Enterprise PR: odoo/enterprise#4605
The currency rate live update feature now supports Chile's SBIF service, allowing businesses to automatically retrieve Chilean exchange rates when they provide an SBIF API token. This reduces manual currency maintenance for companies operating in Chile and keeps financial rates more current.
Original PR description
This adds sbif connection to "currency_rate_live" module. It requires an API Token. It can be obtained from SBIF site.
Enhancements to existing features
Odoo now uses the same fiscal position lookup method across accounting, sales, purchasing, point of sale, repairs, and website sales. This improves consistency in how taxes and accounts are selected for customers and vendors, reducing the risk of mismatched fiscal treatment across different business flows.
Original PR description
Always use get_fiscal_position and not property_account_position_id in Odoo codebase And some cleanups in account: * map_tax supports empty self * get_fiscal_position returns a fiscal position recordset, not an id/False anymore -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Manufacturing orders can no longer be created through the calendar’s quick-create shortcut. This avoids confusing entries where the typed summary is replaced by the system-generated order number, leading users toward the full creation flow instead.
Original PR description
Task-https://www.odoo.com/web?#id=2052536&action=333&active_id=1519&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.a0298c6e2160bc653a9c533b108f364a -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Odoo now handles missing or deleted default activity types more gracefully by falling back to a standard activity instead of raising errors. It also prevents deletion of activity types that are still needed by HR plans or automated server actions, reducing disruptions in workflows that rely on scheduled activities.
Original PR description
**Update of https://github.com/odoo/odoo/pull/32446** If a user deletes one of the default activity types of odoo, a bunch of ref to the xmlid of the activity type may cause errors. To allow more…
**Update of https://github.com/odoo/odoo/pull/32446**
If a user deletes one of the default activity types of odoo, a bunch of ref to the xmlid of the activity type may cause errors.
To allow more flexibility, this a fallback mechanism is implemented in mail.activity.mixin s.t. when calling activity_schedule(xmlid, ...), if the given xmlid is not found, default_activity_type() specifies the default activity (and can be overridden in classes using the activity mixin).
```python
def _default_activity_type(self):
"""Define a default fallback activity type when xml id not found
only used in in activity_schedule() for now.
"""
try:
return self.env.ref('mail.mail_activity_data_todo')
except Exception:
return False
```
- Prevent deletion of activity type (hr.plan and ir.actions.server)
- Fallback on default activity type if xmlid ref not found in activity_schedule
- Correct calls to activity_schedule and replace some create calls by activity_schedule
Task ID : 1961156
Enterprise PR: https://github.com/odoo/enterprise/pull/6238
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThe French chart of accounts now includes tags that classify accounts into operating, financing, investing, and extraordinary activities. This improves the accuracy and usability of cash flow and financial reporting for French accounting users.
Original PR description
Description of the issue/feature this PR addresses: added tag in accounts for 'compte de résultat' financial report Task: https://www.odoo.com/web#id=1973937&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.67e8ba0a372f7f82bba0680aa9067602 Current behavior before PR: Desired behavior after PR is merged:
The Norwegian localization now uses the newer RF-0002 format for financial tax reporting. This helps businesses in Norway align their Odoo reports with updated reporting requirements and reduces manual adjustments during compliance processes.
Original PR description
Task : https://www.odoo.com/web#id=1969011&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.27eb04e13e8e3e3e624b0d80e13acb2a -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Point of Sale sessions now keep and show the actual cash closing difference after validation. This helps store managers review the real end-of-session cash variance later instead of seeing it reset to zero.
Original PR description
Description of the issue/feature this PR addresses: We want to see the real ending cash balance in the pos session form when the session is closed. Current behavior before PR: When we close the pos session, once you click "validate closing & post entries", the difference is transfered to transaction and the difference set back to zero. We don't store the real diff before the calculation and once the session is closed we always see a difference of 0. Desired behavior after PR is merged: When the pos session is closed, we now display the correct ending difference before the validation. Task-Id: 2032173 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Mobile users can now add new columns directly from Kanban views, making board management possible without switching to desktop. This improves usability for teams managing workflows on phones or tablets.
Original PR description
Task:https://www.odoo.com/web#id=1893137&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.39bed8937b446b5c076185288f5f6e1b -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Time off types can now use different approval paths for allocation requests and actual leave requests. This lets businesses route allocation approvals to the right manager or officer without changing who approves employees taking time off.
Original PR description
Purpose ======= We want to allow different approvals for allocations and leaves of a same type. e.g. In case of compensation days, a manager would approve the allocation request, but would later not…
Purpose ======= We want to allow different approvals for allocations and leaves of a same type. e.g. In case of compensation days, a manager would approve the allocation request, but would later not approve leave requests. Specification ============= Allocation modes ---------------- No change here except renames. 1. No limit (employee doesn't need an allocation to request a leave) 2. Allow employee requests 3. Fixed by Time Off Officer Allocation approval ------------------- A radio field to choose the approval mechanism appears if the employee is allowed to request an allocation. The following approval modes are possible: 1. Time Off Officer 2. Employee's Time Off Manager (leave_responsible_id) 3. Employee's Time Off Manager and Time Off Officer These options are the same as leave approval options (except the missing "No Validation"). If option 1 or 2 is selected, a o2m field should allow to select which Time Off Officer is responsible for approving those allocations. Allocation approval policy is the same as the leave approval policy. Task id: 1936742 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Mobile users can now add new columns directly in kanban views using a plus button in the tab bar. This improves setup flows such as creating project stages, especially when a new project has no columns yet.
Original PR description
On mobile, there was no way to create a new column in the kanban view. This was specifically annoying in the Project app (the user was able to create the project but couldn't set its stages). This commit enables this feature by adding a `+` icon at the end of the tabs. This button opens a quick-create column widget. If there is no existing column (for example in a newly created project), this quick-create column widget is opened by default. Finally, this commit improves the processing needed for the swipe animation between the columns. Task ID: 1893137
Survey management has been streamlined to better show quiz scores and the last page reached by respondents. The underlying survey logic was also cleaned up to reduce unnecessary background calls, improving maintainability and day-to-day usability.
This pull request updates the Survey app, touching response handling, survey page behavior, submission logic, and related page assets. The available title and commit message do not describe the business goal, so the change appears to be a small survey-related adjustment rather than a broad functional rollout.
This update standardizes how automated activity reminders are created across several business apps, making them easier to manage and clean up. It also improves default activity type selection so users get more consistent follow-up behavior and reduces the risk of important activity types being deleted incorrectly.
Original PR description
**Update of https://github.com/odoo/enterprise/pull/4032** - hr.approval : default activity_type - Fixes/Clean on activity creation in some modules Task ID : 1961156 Community PR: https://github.com/odoo/odoo/pull/39013 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update makes fiscal position selection and tax mapping more consistent across related sales, marketplace, subscription, and inter-company workflows. Businesses should see fewer tax mismatches when orders or subscriptions are created through different channels.
The French financial report for the profit and loss statement now better classifies accounts using activity tags such as operating, financing, investing, and extraordinary activities. This makes the report clearer and more useful for reviewing business performance in France.
Original PR description
Improve financial report "compte de résultat" Task: https://www.odoo.com/web#id=1973937&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.67e8ba0a372f7f82bba0680aa9067602
Resolved issues and error corrections
Out-of-office messages now show the true return date when an employee has back-to-back leave periods, even if they use different leave types or the leave spans a weekend. This prevents colleagues from expecting someone back too early and improves planning around employee availability.
Original PR description
Description of the issue/feature this PR addresses: Task: https://www.odoo.com/web#id=2002525&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.8af0c15014b1a6004e4f2456cca069ee 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
Odoo now validates standard views even when they have been marked as protected from updates in the database. This helps catch broken screen layouts during module upgrades instead of letting invalid views remain unnoticed.
Original PR description
I tried to write a detailed yet understandable commit message. I failed. The point is that views set to `noupdate` in database were not validated. This is the case since OpenERP 8.0. They are now.
Canceled customer invoices are now excluded from bank reconciliation suggestions. This prevents users from accidentally matching payments to voided invoices and keeps reconciliation results accurate.
Original PR description
Steps to reproduce the bug: - Let's consider customer P - Create two customer invoices C1 and C2 for P - Cancel C1 - Go to bank reconciliation - Create a statement with a line for P - Click on 'Reconcile' Bug: C1 was suggested to be reconciled opw:2120756
Features or functions removed from Odoo
Cancelling a sales order in Odoo will no longer send a cancellation request to Amazon. This prevents accidental Amazon order cancellations during routine Odoo cleanup or resynchronization, while cancellations made on Amazon can still be reflected back in Odoo.
Original PR description
As of this commit, the cancellation of a sales order in Odoo no longer sends a cancellation notification to Amazon. It remains possible to synchronize the cancellation of an order from Amazon in Odoo.
The incentive is that synchronizing order cancellations from Odoo is:
* confusing: Apart from pickings, no data is ever sent to Amazon so users don't expect any action to take place after hitting 'cancel' on a sales order.
* dangerous: Cancelling a sales order is a required step to delete it, which may happen if a user wants to synchronize it again. If the related cron happens to run between the two steps, a cancellation notification will be sent to Amazon even if it wasn't intended.
task-2081442