Thursday, March 20, 2025
11 changes · 18.0
Enhancements to existing features
Point of Sale orders now automatically enable invoicing when a company customer is selected. This reduces manual steps for staff while still allowing them to turn invoicing off when needed.
Original PR description
After this commit, when a company is selected, the order is set to "to_invoice = true" by default. The user is still able to put it back to false if he wants. task-id: 4658640 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The partner autocomplete feature now uses Dun & Bradstreet as its main company data provider instead of Clearbit, improving the reliability of suggested company information. Clearbit remains in use only for company logos, while data lookups are routed to the newer provider through Odoo's IAP service.
Original PR description
We are switching away from Clearbit which is very unreliable. For that reason we had an autosync feature which would update IAP's data for a company based on the data provided in Odoo. Instead, we are now switching to Dun & Bradstreet which has much more reliable data. Some routes have been changed to target the new API on IAP. We continue to use Clearbit for the logos which are not provided by DnB (yet). This is a backport of https://github.com/odoo/odoo/pull/196373 where models, fields, and public methods have been kept to respect the stable policy. task-4416928
Partner autocomplete now uses Dun & Bradstreet for company data instead of Clearbit, improving the reliability of business information suggested in Odoo. Clearbit remains in use only for company logos until the new provider supports them.
Original PR description
We are switching away from Clearbit which is very unreliable. For that reason we had an autosync feature which would update IAP's data for a company based on the data provided in Odoo. Instead, we are now switching to Dun & Bradstreet which has much more reliable data. Some routes have been changed to target the new API on IAP. We continue to use Clearbit for the logos which are not provided by DnB (yet). This is a backport of https://github.com/odoo/odoo/pull/196373 where models, fields, and public methods have been kept to respect the stable policy. task-4416928
The Zomato and Swiggy point-of-sale integrations now look up tax group names dynamically instead of relying on fixed labels. This helps keep tax calculations accurate when tax labels change, reducing maintenance effort and avoiding future configuration issues.
Original PR description
**=pos_urban_piper_swiggy Following this commit: ==== - Previously, static values like 'CGST' and 'SGST' were used. However, 'SGST' has been renamed to 'SGST/UTGST'. - To prevent similar issues in the future, tax group names are now fetched dynamically instead of using hardcoded values. - This ensures accurate tax computation and better maintainability. task-4626494
Resolved issues and error corrections
Global discounts on sales orders now exclude fixed taxes such as ecotaxes from the discounted amount. This ensures legally or operationally required fixed charges remain payable even when a product is fully discounted.
Original PR description
When applying a global discount on a sale order, the fixed taxe shouldn't be consider in a discount. It might be counter intuitive, as a x% discount isn't a discount on the total amount but of the total fixed taxe excluded amount, but is how it should be done. Consider a 100% discount with a product with an ecotax: the ecotax needs to be paid, the sale order can never go down under that amount, yet the product is 100% discounted. opw-4584784
Changing the operation type on a manufacturing order now also updates the related stock move locations. This prevents materials and finished products from being routed through the wrong warehouse locations, improving inventory accuracy.
Original PR description
When picking type is changed, the locations on the moves should also be updated. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents users from changing products on sales order lines after the order has reached a state where those edits should no longer be allowed. It closes a loophole where using multiple browser tabs or simultaneous edits could bypass the normal read-only protection and cause unintended order changes.
Original PR description
If you open the same SO in two different tabs, confirming it in one tab while further modifying it in the other, the readonly restriction won't be considered and you might shoot yourself in the foot by modifying something you shouldn't have. This commit makes sure the product cannot be modified on order lines where it's not supposed to be possible (unless you try to be smart/dumb by opening it in two tabs, or two salesmen are modifying it separately). opw-4595008 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix ensures combo products sold through Point of Sale are invoiced without unnecessary zero-value lines. It makes invoices clearer and helps avoid issues with electronic invoicing requirements.
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
The Project Gantt view now opens correctly even when a user's working schedule is empty. This prevents users from being blocked by an error when viewing project timelines for teams with flexible or missing schedules.
Original PR description
…with empty working schedule **Issue** When setting the working schedule to empty, opening the Gantt view is not possible as an error is displayed Steps to Reproduce: 1. Login as Mitchell Admin 2.…
…with empty working schedule **Issue** When setting the working schedule to empty, opening the Gantt view is not possible as an error is displayed Steps to Reproduce: 1. Login as Mitchell Admin 2. Install Employees and Project apps 3. Go to Employees > Contracts 4. Select a contract from Mitchell Admin 5. Empty the Working Schedule Field 6. Set Planning or Attendances as work entries > Save 7. Go to project app 8. Select a project 9. Switch to the Gantt view 10. An error message appears 11. Expected Behavior: Gantt view should be displayed without errors. Actual Behavior: Gantt view is not displayed, and an error message appears. **Root Cause** The issue occurs because before processing the work intervals, the system checks for the presence and uniqueness of a calendar. If a user has no assigned schedule, the function attempts to process a None value, which results in an error when calling ensure_one in _attendance_intervals_batch. **Fix** To prevent the error, users without a working schedule are skipped when computing valid work intervals. If a user has no assigned schedule, they will not be included in _work_intervals_batch, ensuring the function executes correctly without attempting to process an empty calendar. opw-4462241
Batch payslip generation no longer fails for employees on fully flexible schedules when their contract has no working schedule. The system now checks each payslip's employee timezone correctly, preventing an error that could block payroll processing.
Original PR description
The bug has been introduced by this commit : https://github.com/odoo/enterprise/commit/4cba2fb58560a95d5ce93eb6e6c1483ef0428ba5 The bug appears when trying to generate batch of payslips with fully flexible working schedules. When the contract linked to the payslip has no working schedule, the check of the timezone is done on the employee linked to the payslip. The fix only consists on taking the employee of each slip instead of taking the employee on self, which was causing a 'singleton expected' error. This commit also contains a test for the related fix in the following related PR: task-4623219
This fix makes online bank connection records visible when they include accounts for a company the user can access, even if the connection itself belongs to another company. It helps multi-company users find and manage the relevant bank synchronization links without losing access when switching companies.
Original PR description
Description of the issue/feature this PR addresses: In a multi-company setup, account.online.link records are only visible based on their own company_id. However, these records can have related…
Description of the issue/feature this PR addresses: In a multi-company setup, account.online.link records are only visible based on their own company_id. However, these records can have related account_online_account_ids that belong to different companies. As a result, when switching to a different company, users cannot see account.online.link records that have child accounts in that company. Current behavior before PR: - account.online.link records are only visible if their company_id matches the user's active company. - If a link has account_online_account_ids in different companies, users in those companies cannot access the parent account.online.link. Desired behavior after PR is merged: - account.online.link visibility is determined by the companies of its related account_online_account_ids. - If an account.online.link has accounts (account_online_account_ids) linked to a company the user has access to, the record will be visible. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr