Daily updates from Odoo
Tuesday, July 2, 2024
6 changes · saas-17.2
Resolved issues and error corrections
Fixes an issue where spreadsheet links to list or pivot views could fail because required context was not passed along. Users can now open these linked views from spreadsheets without encountering errors.
Original PR description
## Description: navigateTo helper function in helpers.js was not passing the context to the action. This commit resolves the problem by ensuring the context is properly passed to the action. task-3880304 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Merging customer or vendor records no longer fails when both partners have the same bank account linked to posted payments. The system now consolidates duplicate bank accounts first, helping users clean up partner records without payment history blocking the process.
Original PR description
Currently, you cannot merge partners if they have bank accounts linked to payments. ### Steps to reproduce 1. Install the `account` module. 2. Create two partners, each having the same bank account…
Currently, you cannot merge partners if they have bank accounts linked to payments. ### Steps to reproduce 1. Install the `account` module. 2. Create two partners, each having the same bank account number. 3. Create and post payments for each of those partners. 4. Attempt to merge those partners. You should be met with the following message: ``` The operation cannot be completed: another model requires the record being deleted. If possible, archive it instead. Model: Journal Entry (account.move) Constraint: account_move_partner_bank_id_fkey ``` ### Cause When merging partners, the system attempts to update all foreign keys referencing the partners being merged. In certain circumstances, this update violates unicity constraints. In such cases, the system simply deletes the records that can't be updated. In our case, the `res_partner_bank` table has the following unicity constraint: `unique(sanitized_acc_number, partner_id)`. When we merge the two partners and the system attempts to update the `partner_id` field on `res_partner_bank`, the constraint is violated because both partners originally had the same account number. The system then tries to delete those bank accounts, but it fails because they are linked to payments (with an `ondelete restrict` clause). ### Fix Identify the bank accounts that are duplicated between the source and destination partners, and merge them before merging the partners. ### Note `_update_foreign_keys_generic` is basically just `_update_foreign_keys` from `data_merge`. `_merge_additional_models` exactly the one from `data_merge` opw-3925952
Online course managers now see a clear prompt if they try to publish certification content without selecting a certificate, preventing an error page. The front-end option to create a new certification during upload was removed so certifications are properly set up through the back office before use.
Original PR description
**Crash Prevention:** Added validation to ensure a certificate is selected before saving and publishing, preventing errors. **Creation Restriction:** Removed the option to create certifications from the front-end to avoid incomplete setups, requiring back-end customization. **Code cleanup**: Remove an unused template. Task-3940344
Indian e-invoicing can now process invoice lines with negative amounts. This fixes an unnecessary restriction, helping businesses handle discounts, corrections, or adjustments more smoothly.
Original PR description
This PR removes the restriction on invoice lines having negative amounts in the `l10n_in_edi` module, which was introduced in PR https://github.com/odoo/odoo/pull/170736. This fix allows invoice lines with negative amounts to be processed, aligning with the intended functionality and ensuring a smoother invoicing experience.
This update brings the spreadsheet component to a newer version with several small fixes. Users should see smoother spreadsheet editing, including better sheet name editing, corrected translation loading, and improved find-and-replace navigation.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/fac2351f9 [REL] 17.2.13 Task: 0 https://github.com/odoo/o-spreadsheet/commit/ef733da35 [FIX] BottomBarSheet: Prevent drag of sheet while editing its name Task: 4010842 https://github.com/odoo/o-spreadsheet/commit/235ff4cc8 [FIX] model: mark default translations as loaded Task: 3999116 https://github.com/odoo/o-spreadsheet/commit/af15d3af3 [FIX] find_and_replace: fix previous command Task: 3839575 Co-authored-by: Anthony Hendrickx (anhe) <anhe@odoo.com> Co-authored-by: Alexis Lacroix (laa) <laa@odoo.com> Co-authored-by: Lucas Lefèvre (lul) <lul@odoo.com> Co-authored-by: Dhrutik Patel (dhrp) <dhrp@odoo.com> Co-authored-by: Adrien Minne (adrm) <adrm@odoo.com> Co-authored-by: Mehdi Rachico (mera) <mera@odoo.com> Co-authored-by: Rémi Rahir (rar) <rar@odoo.com> Co-authored-by: Pierre Rousseau (pro) <pro@odoo.com> Co-authored-by: Vincent Schippefilt (vsc) <vsc@odoo.com>
This fix prevents a confusing failure when confirming a sales order if a delivery operation has no default destination location set. Users are now guided more clearly to correct the stock configuration, helping avoid blocked deliveries after upgrades or manual setup changes.
Original PR description
Steps to reproduce: - Enable locations in Stock settings - Edit delivry order picking type in Inventory overview - Edit the form view and remove required from default_location_dest_id - Set Default Destination Location to blank - Create and confirm a new SO Bug: default_location_dest_id is only required on the frontend if not set an error is thrown when confirming an SO (impossible to create the move) Fix: -Stable: upgrade script has already been fixed https://github.com/odoo/upgrade/pull/5873 but it's better to still add a more userfreindly redirect for customers that upgraded before the PR was merged (particularly since it's still possible to mess it up as the field is not required on the backend) -Matser: set the field as required on the backend aswell opw-3970295