Tuesday, May 19, 2026
35 changes · saas-19.3
New functionality added to Odoo
This update allows users to easily insert their personalized profile signature into emails directly within the Odoo editor. This improves email communication by allowing users to add a professional touch. The existing signature functionality for Email Marketing & Knowledge remains unchanged.
Original PR description
Purpose of this PR: - Add a new Signature command to insert the user's profile signature defined in user preferences. This is handled by UserSignaturePlugin and and is part of the main editor plugins. - Keep the existing Signature plugin restricted to Email Marketing & Knowledge. task-6127297 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#260279
Enhancements to existing features
This update enhances the Windows IoT version tracking by automatically recording the build date in a VERSION file, mirroring the format used for Raspberry Pi IoT images. This ensures consistent versioning and simplifies identifying the specific build of the IoT installation. Additionally, the Windows version is now logged upon startup for easier monitoring.
Original PR description
Before this commit, the Windows IoT version was hardcoded to '23.11'. After this commit, the installer now writes a VERSION file to the IoT install directory (which will remain between git checkouts). This file contains the build date in `YYYY.MM.DD` format, the same as the current Raspberry Pi IoT images. In addition, the Windows version is now logged on startup. task-6196801 **Image version:** <img width="306" height="39" alt="image" src="https://github.com/user-attachments/assets/f0252d44-4b5c-4bb5-aac8-4b8f56dc6ee2" /> **Windows version:** > INFO ? odoo.addons.iot_drivers.main: Windows version: Windows-11-10.0.26100-SP0 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#263392 Forward-Port-Of: odoo/odoo#263089
Resolved issues and error corrections
This update resolves an issue with the alignment of payrun details within the Odoo Enterprise system. The team removed unnecessary code and corrected the layout to ensure payrun information is displayed accurately. This improves the user experience and data clarity for payroll processing.
Original PR description
Remove useless classes and fix alignment task-6191499
Documentation and clarification updates
This pull request implements a Corporate Legal Agreement (CLA) for QoQa, ensuring compliance with Odoo's contribution guidelines. The change was backported from version 18.0 to meet compatibility requirements. This update strengthens Odoo's legal protections and clarifies the terms of QoQa's use of the platform.
Original PR description
Description of the issue/feature this PR addresses: This is the corporate CLA for QoQa. I backported #262581 because we need it from 18.0 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#262582
Miscellaneous changes
This pull request represents a routine automated check (linting) across several Odoo modules – delivery, loyalty, and payment – to ensure code quality and consistency. The changes are purely a confirmation that the code adheres to Odoo's coding standards and guidelines, without introducing any new functionality or fixing bugs. This ensures a stable and reliable user experience.
Original PR description
post freeze run for task-5436779 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update ensures that new fields added to the planning slot template – specifically company ID and worksheet template ID – are thoroughly tested. These tests were created to maintain code quality and prevent potential issues related to these template configurations within the Odoo Enterprise system.
Original PR description
The purpose of this commit is to ensure that the code of the following PR: https://github.com/odoo/enterprise/pull/112198 is properly tested. We add tests related to the addition of the `company_id` field on planning.slot.template, as well as the addition of `worksheet_template_id` field. task-6147827
This update enhances how Odoo handles database errors during safe evaluation. By catching and retrying `IntegrityError` exceptions, the system now behaves more consistently regardless of the code being executed, leading to more reliable operations. This improves overall system stability and reduces potential disruptions.
Original PR description
It makes sense to bubble up the `psycopg2.IntegrityError` (as well as the subcase `ConcurrencyError`) so that the retry mechanism can handle this exception. In fact, this exception can be triggered without necessarily a problem with the "logic/business code". This ensures consistent behavior between the business logic and the code executed in `safe_eval`. Task-6215886 Forward-Port-Of: odoo/odoo#264838 Forward-Port-Of: odoo/odoo#264266
This update fixes an issue where the print button disappeared from PDF attachment previews in version 19 and later. The change removes a redundant setting that was previously hiding the print button on desktop, ensuring it's consistently visible for all users. This restores a key functionality for accessing and printing PDF documents.
Original PR description
**Problem:** When opening a PDF attachment preview in v19+, the print button disappeared. As a result, the Print button is not accessible from the main toolbar. In v18 the buttons remained…
**Problem:** When opening a PDF attachment preview in v19+, the print button disappeared. As a result, the Print button is not accessible from the main toolbar. In v18 the buttons remained permanently visible. **Steps to reproduce:** - Open any record that has a PDF attachment in the chatter. - Click the PDF attachment to open the preview popup. - Observe toolbar buttons disappeared. **Cause:** commit responsible for this: https://github.com/odoo/odoo/commit/b7889d007f72c7e7f9f22318a9968338cde0ddb3 It was removed to prevent some bugs with some android/smartdevice and some old browsers `file_viewer.js` passes `hidePrint: true` to `hidePDFJSButtons()`. This was originally added alongside the mobile guard (`isMobileOS()`), but the `isMobileOS()` guard in `hidePDFJSButtons` already handles mobile, so the explicit `hidePrint: true` in `file_viewer.js` was redundantly hiding Print on desktop too. https://github.com/odoo/odoo/blob/654a1caafc2ab7b2841c372910b2e81dc6e9c035/addons/web/static/src/core/file_viewer/file_viewer.js#L60-L71 https://github.com/odoo/odoo/blob/654a1caafc2ab7b2841c372910b2e81dc6e9c035/addons/web/static/src/core/utils/pdfjs.js#L35-L37 **Fix:** - Remove `hidePrint: true` from `file_viewer.js` since mobile is already covered by the `isMobileOS()` check inside `hidePDFJSButtons()`. opw-6216534 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#264739
This update aligns the subheaders and numerical data within Odoo's financial reports, ensuring a more consistent and professional appearance. Previously, the alignment was inconsistent, making the reports less readable. This change improves the overall user experience and data presentation.
Original PR description
Before this commit, subheaders of numeric columns were centered, while the figures in the columns were aligned to the end. This commit ensures that both the subheader and the figures are aligned the same way (center or end). task-6197223 Forward-Port-Of: odoo/enterprise#117477 Forward-Port-Of: odoo/enterprise#116578
This update fixes a UI inconsistency in the property editing process. Previously, the "Add Property" button would remain visible even when switching between records or creating new ones. Now, the button correctly resets to "Edit Properties" ensuring a smoother and more intuitive user experience when managing properties.
Original PR description
Before this commit: - The “+ Add Property” button was not visible when switching between notebook pages if it was present initially. - when we are doing edit properties from the cog menu and without doing save properties if we are creating new record or switch to other record at that time button still shows “Save Properties.” leading to inconsistent UI behavior. After this commit: - The “+ Add Property” button remains visible when switching between pages. - When in property edit mode, switching records or creating a new record now correctly resets the button state back to “Edit Properties”, ensuring consistent UI behavior. task-6051322 ENT PR: https://github.com/odoo/enterprise/pull/113248 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#258030
This update fixes a UI inconsistency in the worksheet property editor. Now, the ‘Add Property’ button remains visible while editing and correctly resets to ‘Edit Properties’ when switching records or creating new ones, ensuring a smoother and more reliable user experience. This resolves a previous issue where the button's state was confusing.
Original PR description
Before this commit: - The “+ Add Property” button was not visible when switching between notebook pages if it was present initially. - when we are doing edit properties from the cog menu and without doing save properties if we are creating new record or switch to other record at that time button still shows “Save Properties.” leading to inconsistent UI behavior. After this commit: - The “+ Add Property” button remains visible when switching between pages. - When in property edit mode, switching records or creating a new record now correctly resets the button state back to “Edit Properties”, ensuring consistent UI behavior. task-6051322 Forward-Port-Of: odoo/enterprise#113248
This update corrects an issue where invoices using a specific tax category ('O-service out of tax scope') in Odoo failed Peppol validation. The fix ensures invoices with this category don't include VAT IDs, aligning with Peppol requirements and preventing validation errors.
Original PR description
**PROBLEM** In peppol, there is a tax category 'O-service out of tax scope'. This tax category is used when what is invoice can't be tax (out of the tax scope). This is different from tax exemption: when using tax category O, there can't be any vat id on the invoice. This also means you can't use tax category O with other taxes, since other taxes need the vat id. Invoices generated by odoo with tax category O failed peppol validation. **STEP TO REPRODUCE** 1. install account_edi_ubl_cii_tax_extension. 2. Create a tax with tax category O. 3. Create an invoice and try validating using the file validator. 4. You should have error BR-O-02 and BR-O-05. opw-6012669 Forward-Port-Of: odoo/odoo#264081 Forward-Port-Of: odoo/odoo#254645
This update fixes a minor issue where some work entry names in the Odoo system were misspelled. The team corrected the data files to ensure accurate and consistent naming conventions for work entries, improving the overall user experience. This change was driven by a reported issue (opw-6090081).
Original PR description
Issue: ---------------------------------------- Some work entry names are wrong. Solution: ---------------------------------------- Change the data files. opw-6090081 Forward-Port-Of: odoo/odoo#264094
This update fixes a visual issue where long accounting reports would cut off the final row, preventing users from seeing all the data. The team adjusted styling to ensure all rows are fully visible, regardless of the report's length. This improves the clarity and completeness of financial reports.
Original PR description
Problem: When an accounting report fills a whole page, the final row is not fully visible Steps to reproduce: 1- View a tax report that has a lot of entries that would fill the whole screen 2- Notice how the last line is not fully visible and it isn't possible to scroll and view the rest of it Solution: Correctly style the different < div > elements opw-6171555 Forward-Port-Of: odoo/enterprise#116068
This update fixes a potential crash in the Gantt chart interface. It reintroduces a safeguard to prevent errors when a user attempts to drag a pill without a valid target. This ensures the Gantt chart remains stable and reliable during testing and user interactions.
Original PR description
In https://github.com/odoo/enterprise/pull/113438, it was incorrectly assumed that it would be impossible to initiate a pill drag without a valid target being found. This commit reintroduces a strict safeguard to handle scenarios where the drag is triggered with no valid cell target. This prevents unexpected crashes encountered during test executions. runbot-error-242486 Forward-Port-Of: odoo/enterprise#116619
This update fixes an issue where Knowledge articles appeared narrow when printed on large screens. The fix specifically targets the Knowledge editor's form view, preventing a CSS rule from causing a constricted layout. Now, articles print correctly in a readable format when exported or printed.
Original PR description
Currently, a CSS rule forces the form container width to 1px to ensure that the nested list view can correctly compute its size. See: ```scss .o_form_view.o_xxl_form_view { .o_form_view_container {…
Currently, a CSS rule forces the form container width to 1px to ensure that the nested list view can correctly compute its size.
See:
```scss
.o_form_view.o_xxl_form_view {
.o_form_view_container {
width: 1px; /* List view needs a width value to recompute the size correctly */
}
}
```
However, since the Knowledge editor is implemented as a form view, this rule also affects Knowledge. When zooming out, the `o_xxl_form_view` class is added to the form view container, causing the rule to apply. If an article is printed while this class is present, it is constrained to an extremely narrow column, making it unreadable.
Steps to reproduce:
1. Open an article in Knowledge
2. Zoom out using `Ctrl` + `-`
3. Open the kebab menu and select "Export"
=> The article is rendered in a very narrow column.
To address this issue, we override this rule specifically for Knowledge. With this change, articles are now rendered correctly when printed or exported as PDF.
Task-5999878
Forward-Port-Of: odoo/enterprise#103259This update corrects issues with the Swedish ISO 20022 XML structure, ensuring accurate data transmission to banks. Specifically, the system now consistently uses BIC identifiers for financial institutions and addresses a unique requirement from Nordea bank regarding bank account formats.
Original PR description
Here is few fixes added to the swedish iso 20022 XML: - CdtrAgt seems to be always mandatory, change the condition in `_skip_CdtrAgt` to always use the CdtrAgt if payment_method is iso20022_se - The `_is_se_bban` is too restrictive, this should be always True when payment method is swedish iso - The `FinInstnId` node can either contain BIC or ClrSysMmbId. But as ClrSysMmbId seems to change from one bank to another, it's more relevant to always use the BIC. opw-5395736 Forward-Port-Of: odoo/enterprise#117574 Forward-Port-Of: odoo/enterprise#114662
This update ensures charts maintain their current granularity when users specify custom date ranges (e.g., 'until 2024-01-01) instead of automatically adjusting based on global filters. Previously, the system struggled to determine the optimal chart level with these specific ranges, leading to potential inconsistencies. This fix guarantees a consistent chart display regardless of the user's date selection.
Original PR description
The charts adapt their granularity when a date global filter is updated. But the code didn't handle the cases where the user sets a custom range with an open start or end date (eg. `until 2024-01-01`). In those case picking the best granularity is not practical (because it fully depends on the server data), so we will just keep the current granularity. Task: [6196246](https://www.odoo.com/web#id=6196246&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form) 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 Forward-Port-Of: odoo/odoo#264939 Forward-Port-Of: odoo/odoo#263019
A recent test failure in the 'pos_self_order' module was caused by how time slots were generated. This update has corrected the issue by freezing the time to midnight, ensuring all available slots are considered during testing. This prevents test failures and improves the reliability of the order scheduling functionality.
Original PR description
Before this commit: = - The test test_slot_limit_orders created slots only for the first day of the week (Monday). - The test scenario includes a slot at "18:00". - On Mondays, the test fails between 18:01 and 23:59 because the "18:00" slot no longer exists for the current day. - On other days, the test passes since slots are generated for the upcoming Monday. After this commit: = - Freezed the time to current day at "00:00" so that slot list can have every slot for that day. task-6043739 runbot-241836 Forward-Port-Of: odoo/odoo#263476 Forward-Port-Of: odoo/odoo#254775
This update fixes an issue where image data lingered in the website builder's code after shapes were removed, leading to potential performance problems. The change adds a cleanup process to remove outdated image data, ensuring a cleaner and more efficient website builder experience. This improves the overall stability and responsiveness of images on the Odoo website.
Original PR description
Steps to see the issue: - Add a shape to an image - Remove it => Image element in the DOM still has some data related to the shape. This commits adds a shared method to `ImageShapeOptionPlugin` to…
Steps to see the issue: - Add a shape to an image - Remove it => Image element in the DOM still has some data related to the shape. This commits adds a shared method to `ImageShapeOptionPlugin` to clean shape-related data when we apply a shape, or remove it, the method mirrors the behavior we had before the [html builder refactoring]. Also, commit [1] fixed the issue when the builder transfered shape or hover related data to incompatible images, when replacing an image with a shape/hover on it. However if these data attributes had already been saved prior to that commit, it would stay there indefinitely. The same could happen with hover effects attributes. Therefore, we add a resource that we call before saving data to clean any stale image data. Example of a CORS protected image: [2] [1]: https://github.com/odoo-dev/odoo/commit/137a6d7e59e1d788745c3b796a14839e52a8c5bc [2]: https://tinyjpg.com/images/social/website.jpg [html builder refactoring]: github.com/odoo/odoo/9fe45e2b7ddbbfd0445ffe25a859e67a316d02b2 task-5172640 Forward-Port-Of: odoo/odoo#263662 Forward-Port-Of: odoo/odoo#259226
This update fixes an issue where the call preview overlay was overlapping with call actions on smaller screens. The change ensures the preview remains fully visible and readable, improving the user experience for all users. This was part of a larger effort to enhance usability across different screen sizes.
Original PR description
Purpose of this PR: Since #235707, the call preview content could overlap the call actions on small screens. This commit prevents the overlap and keeps the preview readable. Before/After: <table> <tr> <td> <img width="398" height="691" alt="image" src="https://github.com/user-attachments/assets/da7eaf5b-387e-439f-80bb-cb6dd8c07454" /> <td> <img width="391" height="691" alt="image" src="https://github.com/user-attachments/assets/384a08d1-6b51-490a-8b57-267a3bb1b3d5" /> </table> task-[6201269](https://www.odoo.com/odoo/project/1519/tasks/6201269) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#263535
This update resolves an issue where users without write access to the AT Point of Sale (PoS) would receive an access error when attempting to authenticate after a token expiration. The fix ensures that the correct access error is displayed, preventing disruptions to sales transactions.
Original PR description
When trying to auth directly from the PoS when the token expires, if you are logged in with a user that doesn't have write access to the PoS. You would get an access error. Steps to reproduce: ------------------- * Setup Fiskaly in an AT company * Open PoS and try to make a sale * To fake the token expiration I modified the code so that the request always return 401 status code > Observation: You get an access error opw-5925203 Forward-Port-Of: odoo/enterprise#115735 Forward-Port-Of: odoo/enterprise#112474
This update resolves an issue where the payroll report would fail if a new employee didn't have a start date defined. The fix ensures the report checks for a start date before attempting comparisons, preventing errors and improving report reliability. This ensures accurate payroll processing.
Original PR description
If there is no start date on the veriosn, the report will fail as it'll try to compare a bool with a datetime. So we check first that there is a start date Forward-Port-Of: odoo/enterprise#117534
This pull request applies automated linting fixes across several website sale modules, including those related to Amazon, Lazada, Shopee, and renting. These fixes ensure consistent code style and formatting, improving code readability and maintainability. The changes are purely technical and do not impact any business functionality.
Original PR description
post-freeze run for task-5436779
This update reintroduces a 'proc title' monitoring feature that was previously removed. This allows the team to better track key performance indicators related to the core system. The change ensures continued visibility into important operational data.
Original PR description
This was removed in ad36284 but is useful for monitoring. 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 resolves an error that prevented the generation of PDF reports for Colombian tax statements. The issue stemmed from a change in how report data is structured, requiring a simple update to access the correct data values. This ensures accurate report generation and avoids disruptions for users generating these reports.
Original PR description
***Steps to reproduce*:** - Install `l10n_co_reports` module. - Create 2 vendor bills with taxes `0% EXEMPT` and `0.966% RteICA`. - Navigate to Reports -> Colombian Statements -> Certificado de…
***Steps to reproduce*:** - Install `l10n_co_reports` module. - Create 2 vendor bills with taxes `0% EXEMPT` and `0.966% RteICA`. - Navigate to Reports -> Colombian Statements -> Certificado de Retención en ICA - Generate the PDF report. ***Observed behavior*:** - An error is raised while generating the PDF: `AttributeError: 'AccountReportColumnData' object has no attribute 'get'` ***Cause*:** After commit [1](https://github.com/odoo-dev/enterprise/commit/b92dc397bef029472a40223f51b611cdf5b631dc#diff-e97f74c63a6257470e69eb8122c12d0ce4afa5bc6013176bb69e702849575123) all report lines, columns, and annotations were converted from dictionaries to custom objects (e.g., AccountReportColumnData). However, the function `_get_report_values` still uses .get() to access values, which is only valid for dictionaries. Calling .get() on these objects raises an error. ***Fix*:** - Replace the `get()` method usage with `column.name` format to access values from `AccountReportColumnData ' properly. - This ensures compatibility with the new structured column data format introduced in v19.2. opw-6205984 Forward-Port-Of: odoo/enterprise#116902
This update fixes an issue where inactive records weren't properly reflected in many-to-many field caches during updates. By ensuring inactive records are included in the cache calculations, the system now maintains a more accurate and complete view of relationships, improving data consistency and reporting. This primarily impacts modules utilizing many-to-many relationships.
Original PR description
see commit message --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The website builder's AI-generated content was causing spacing issues due to overly broad spacing rules. This update refines the AI's rules to focus solely on new layout changes, ensuring existing snippet structure and classes are preserved during content edits. This improves the visual consistency and usability of the website builder.
Original PR description
Snippets added by AI have its elements glued with no proper spacing. The problem is the spacing rule in the builder topic was too broad and implied existing Bootstrap margin or gutter classes should be removed, even when only editing snippet content. Limit the rule to new layout spacing changes and tell the AI to preserve existing snippet structure/classes during content-only edits. task-id-6230199
This update fixes an issue where the spreadsheet feature was making unnecessary server requests when displaying CRM lists. By ensuring all required data is fetched directly within the spreadsheet's data source, we've significantly reduced the number of calls to the server, resulting in faster loading times and a smoother user experience. This improves overall spreadsheet performance.
Original PR description
How to reproduce: - Create a spreadsheet with a CRM list and only set 2 cells content A1: =odoo.list(1, 1, "id") A2: =odoo.list.header(1,"zip") - save and reload the spreadsheet and look at the server calls ⮕ web_search_read called 2 times The problem is that the datasource methods early return if the datasource is already loading without adding the field to the list to fetch. It was partially solved by explicitely adding the field to fetch in the *getter* `getListCellValueAndFormat` but not on `getListHeaderValue`. This revision ensures that we always add the field to the list to fetch in the datasource directly, this responsibility should not be held by the plugin getters. Task-6175523 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 Forward-Port-Of: odoo/odoo#261985
This update fixes a technical error that prevented QR invoices from printing correctly for Swiss companies. The issue stemmed from an incorrect function call within the invoicing module, which was resolved by correcting the code syntax. This ensures all invoices with QR codes can now be printed successfully.
Original PR description
**Steps to reproduce:** - Install the `l10n_ch` module and switch to a `CH Company`. - Go to Invoicing Settings and enable `QR Codes`. - Create a new invoice for the CH Company. - In the `Other Info` tab, set `Payment QR-code` to `Swiss QR bill`. - Confirm it and click `Print`. **Error:** `TypeError: '_VirtualList' object is not callable` **Root Cause:** At [1], the code incorrectly calls `pages` as a function using `round brackets`. However, pages is a `_VirtualList` `object` that only supports index-based access using `square brackets`. **Fix:** This commit prevents the traceback and ensures that invoices can be printed successfully. [1]: https://github.com/odoo/odoo/blob/2b486f35235974584b3434c2ca93297db802ae81/addons/l10n_ch/models/ir_actions_report.py#L57-L58 opw-6215049 opw-6221311 opw-6242083 opw-6246101 opw-6244005 opw-6240997 opw-6224433
This update corrects a minor issue where holiday requests weren't always correctly associated with the version of Odoo being used. Now, the system accurately tracks and manages holiday requests based on the current Odoo version, ensuring accurate scheduling and reporting. This improves the reliability of our HR data.
Original PR description
…ion being written on 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 Forward-Port-Of: odoo/odoo#264997
This update resolves an issue preventing non-administrator users from viewing user settings within the Odoo Enterprise system. Previously, users lacked access to the 'Settings/Users' view, restricting their ability to manage user accounts. This change ensures all users can access essential user management features.
Original PR description
Steps:
- Create a user X with admin rights
- Connect as X
- Open Settings/Users
- Access right error
```
Failed to read field res.users.database_user_ids
You are not allowed to access 'Database User' (databases.user)
```
opw-6209241
Forward-Port-Of: odoo/enterprise#117573This update removes unnecessary progress reporting from Odoo's automation and autovacuum processes. Previously, these processes were incorrectly signaling progress, leading to redundant and potentially problematic retries. This change enhances the stability and efficiency of Odoo's background jobs.
Original PR description
Base automation and autovacuum should not log progress as this is makes the job scheduler think that something progresses and can be retried leading to the same error because we process the same (all) items. In general, progress numbers are only relevant for jobs that act as job queues. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#264684
This update resolves a problem that prevented users from successfully upgrading their Odoo system when updating tax account tags. The fix replaces a problematic process with a simpler method to ensure tax account information is correctly updated after an upgrade, improving system stability and preventing upgrade failures.
Original PR description
When a module depends on `l10n_account_withholding_tax` and updates tax account tags on the chart of accounts, the upgrade fails. `_withholding_tax_get_demo_account_ref` calls `_get_account_tax`, which calls `_deref_account_tags`, throwing an error due to missing tags in the database since the deref tags function dri. This occurs because the depening module tags has not updated yet as it needs to be triggered by the user post upgrade. This fix uses `_parse_csv` instead to avoid calling `_deref_account_tags` and triggering the issue. task-4967527 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#265239
This pull request incorporates code contributions from BMyA, following our standard legal agreement process (CLA). The changes relate to integration with blancomartin.cl and bmya.cl, ensuring compliance with our open-source licensing. This update supports a new partnership and maintains our commitment to secure contributions.
Original PR description
New contributors from BMyA --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#261658