Thursday, December 19, 2024
16 changes · 17.0
Resolved issues and error corrections
This fixes an issue where selection pop-ups could ignore filters set on multi-record fields. Users will now only see the relevant records in the dialog, reducing mistakes and improving data entry consistency.
Original PR description
When using MultiRecordSelector with domain, the domain will not automatically apply to SelectCreateDialog. See odoo/enterprise#68484 closes odoo/odoo#176850 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 brings the spreadsheet component to a newer version with fixes for formatting, Excel import/export, sheet history, and figure handling. Users should see fewer crashes and better preservation of spacing and line breaks when working with spreadsheets or Excel files.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/820f3cfc2 [REL] 17.0.44 Task: 0 https://github.com/odoo/o-spreadsheet/commit/40afed18b [FIX] cell: keep non-breaking…
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/820f3cfc2 [REL] 17.0.44 Task: 0 https://github.com/odoo/o-spreadsheet/commit/40afed18b [FIX] cell: keep non-breaking spaces Task: 4403607 https://github.com/odoo/o-spreadsheet/commit/e2c9c487a [FIX] sheet view: DELETE_SHEET in initial revisions Task: 4405573 https://github.com/odoo/o-spreadsheet/commit/e735de913 [FIX] xlsx: preserve leading whitespace at export Task: 4044862 https://github.com/odoo/o-spreadsheet/commit/a6a3eeb7c [FIX] xlsx: import new lines in sharedStrings Task: 4044862 https://github.com/odoo/o-spreadsheet/commit/434bbae58 [FIX] figure: crash on deleting dragged figure Task: 4329240 https://github.com/odoo/o-spreadsheet/commit/4ec1734da [FIX] composer: topbar composer z-index Task: 4246966 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 fixes an issue in Web Studio where the editing toolbar could drift away from selected text while the page was scrolled. The toolbar now remains aligned with the original selection, making text editing more predictable and easier for users.
Original PR description
**Current behavior before PR:** - In web studio, when text is selected and the page is scrolled, the toolbar does not stay aligned with the selected text. **Desired behavior after PR is merged:** - Now, when scrolling in web studio, the toolbar remains fixed to the initial selection. task-4317313
Spreadsheet dashboard translation exports now include newer spreadsheet file formats that were previously skipped. This helps ensure dashboard labels and terms are available for translation, reducing missing text in localized Odoo deployments.
Users now see a clearer, friendlier warning when trying to assign a parent to the protected base analytic plan "Projects." This helps avoid confusion from a generic system error and makes the restriction easier to understand.
Original PR description
Steps to reproduce: - Try to add a parent to the base plan "Projects" Issue: Unclear error message Cause: This is a master data and the constraint raised an unclear message "Invalid Operation This column contains module data and cannot be removed!" https://github.com/odoo/odoo/blob/1621f12e90b5903d1132875db7b0d94fa68bc642/odoo/addons/base/models/ir_model.py#L857-L859 Solution: We specify a more user-friendly message during the onchange opw-4327913
The point of sale Viva Wallet integration now checks payment sessions directly when the usual webhook callback does not arrive. This helps ensure successful or failed payments are reflected in Odoo instead of leaving orders waiting indefinitely.
Original PR description
The Viva Wallet integration relies on Odoo being called by Viva Wallet via a webhook. There have been many issues of this webhook never being called, and therefore payments getting stuck in Odoo. In this commit, we add a polling fallback. Every 5 seconds we query the Viva Wallet session, and if we get a response (success/failure) then we update the payment state in the PoS. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update corrects a problem in the CRM team member area. It helps keep sales team membership behavior more reliable for users working with CRM records.
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 French tax report now opens the correct tax journal entries when users review the “VAT Due” section. This makes the detailed debit and credit view match the report total, reducing confusion during VAT review and reconciliation.
Original PR description
[FIX] l10n_fr: add tax move lines in tax report In the l10n_fr tax report, the wrong `account_move_line` entries are used in the journal item list view of the tax report in section `TD-VAT Due`. As a…
[FIX] l10n_fr: add tax move lines in tax report In the l10n_fr tax report, the wrong `account_move_line` entries are used in the journal item list view of the tax report in section `TD-VAT Due`. As a result, the balance debit/credit displayed under the `TD-VAT Due` is not the same as the balance in the journal items list view. - Create a customer invoice with a price 1000 and a tax 20% Goods. - Create a vendor bill with a price 100 and a tax 20% Goods. - Open the tax report, under the TD - VAT Due, the balance is 180. - Click on the amount in TD - VAT Due, the debit is 20 but the credit is 1000 (should be 200). The formula for `TD-VAT Due` is defined as `box_16.balance - box_23.balance`. - `box_16` is the sum of box_xx.balance which are defined by `account_tag`. - The balances of these boxes were computed using the base `account_tag`, which calculates the correct amount but causes `_expand_aggregations` in `account_report_expression` to generate a list view based on base move lines instead of the corresponding tax lines. This can be seen the label field of the lines, which are not the tax label. `box_16` needs to be computed using `box_xx_taxe` instead of `box_xx_base` to ensure the correct tax lines are included. For box 08, 09, 9B, 10, 11, T1, T2, T3, T4, T5, T6, P1, P2, I1, I2, I3, I4, I5, I6 we replace balance to balance_from_tags (which uses box_xx_taxe) For box 13, 14, 15, T7, 5B we keep balance (which already uses box_xx_taxe) opw-4335396 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
A test file used by the accounting tests is now created with content instead of being empty. This prevents related automated tests from failing unexpectedly, helping keep accounting changes reliable.
Original PR description
test file in test_preserving_manually_added_attachments function is being created empty, and because of that some of the tests are breaking. This commit fixes the issue. [link to broken builds](https://runbot.odoo.com/odoo/action-573/110710) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Point of Sale customer search now uses additional customer details when looking beyond the customers already loaded in the session. This helps cashiers find customers by ZIP code more reliably, reducing lookup failures at checkout.
Original PR description
Currently, when searching the through the customers loaded in pos you can search using the zip code but if the customer is not loaded you cannot search those in db using the zip code. Steps to reproduce: ------------------- * Create a customer and set his zip code. * Open pos shop * Search for customers * Enter the zip code, normally you shouldn't see the customer * Select "Search more" > Observation: No customer found Note: If you search with the customer name it will find it. Why the fix: ------------ Adding a few search values when loeading customers in the session. opw-4334412
This update resolves a technical issue preventing users from accessing account data correctly. The fix ensures that currency information is properly handled, eliminating a serialization error that was causing disruptions. This improves the reliability of the account synchronization process.
Original PR description
This commit resolves an issue where users encounter a serialization error when attempting to retrieve accounts. The currency_id is now correctly passed and managed to prevent the "currency object is not serializable" error. no task id Forward-Port-Of: odoo/enterprise#75908
This update resolves an issue where caliper devices were generating error popups due to attempts to read measurement values. The team implemented a fix within the caliper drivers to handle continuous measurements without causing errors, ensuring accurate data capture.
Original PR description
`quality_iot` listens continuously for measure updates. It also provides a "take measure" button for devices that don't send automatically their measure. On caliper devices, measures are sent continuously, so methods to read value once were not implemented, resulting in a error if we tried to call them. To avoid displaying an error popup, we implemented those actions on caliper drivers. opw-4332476
This update fixes an issue where credit notes were incorrectly appearing in the invoices section of the Tax Report 349 (Mod 349) for ES companies. The fix ensures that credit note amounts are now correctly displayed in the refunds section, aligning with ES tax reporting requirements for intra-Community operations. This improves the accuracy of tax reporting data.
Original PR description
In ES localization Tax Report 349 is an informative tax return report for intra-Community operations. Currently, the tax report will show amounts from credit notes in the invoices section, instead of the refunds section Steps to reproduce: - Have an ES Company setup - Create and confirm credit note with: - EU partner - Type for mod 349: A - Go to Accounting > Reporting > Tax Report - Select Report: Tax Report (Mod 349) (ES) Issue: Credit Notes appear in the invoices section instead of the refunds section opw-4358330 Forward-Port-Of: odoo/enterprise#75266
This update resolves an issue in Odoo's web studio where the toolbar would misalign when scrolling with selected text. Now, the toolbar remains fixed to the initial selection, providing a more consistent and user-friendly experience while editing reports. This improves usability and reduces frustration for users.
Original PR description
**Current behavior before PR:** - In web studio, when text is selected and the page is scrolled, the toolbar does not stay aligned with the selected text. **Desired behavior after PR is merged:** - Now, when scrolling in web studio, the toolbar remains fixed to the initial selection. task-4317313
This update corrects a previous issue where the document type field was incorrectly being applied to customer invoices. Now, the system only calculates this field for customer invoices, ensuring accurate reporting and compliance. This change maintains the standard functionality for all other document types within the Odoo Enterprise system.
Original PR description
Users only need the computation of the document type field for customer invoices. As a result, this fix restricts the assignment of document types to customer invoices, while preserving the standard functionality for all other document types. task-4299210 This is a fix for #73945 Forward-Port-Of: odoo/enterprise#75335
This update corrects a previous issue where translations were missing from spreadsheet dashboard files, ensuring accurate localization for key business modules. The commit re-exports the necessary translation files to resolve this and maintain consistent I18N across the Odoo Enterprise platform.
Original PR description
The related community commit fixed the issue where we forgot to extract terms from spreadsheet files ending in "_dashboard.osheet.json" and were file references were added multiple times in the .pot files. This commit re-exports all spreadsheet pot files again using the fixed code. Related to https://github.com/odoo/odoo/pull/190598
Original PR description
Currently, the extractor looking for terms to translate in spreadsheet files was specifically looking for files ending in "_spreadsheet.json". However, since this version there were new spreadsheets added that ended in "_spreadsheet.osheet.json". The translation extractor couldn't find these and the terms were never extracted, resulting in missing translations. This commit searches for both filename patterns to export the terms. We also make sure that file references are only extracted once per term per file. Related to https://github.com/odoo/enterprise/pull/75605