Daily updates from Odoo
Saturday, March 7, 2026
24 changes
5 changes
Resolved issues and error corrections
This update resolves an issue where Romanian customers without a company registry were incorrectly assigned the default VAT instead of the standard VAT. The fix removes a redundant condition that was causing this misassignment, ensuring accurate VAT application for all Romanian customers.
Original PR description
Problem --------- In a recent fix, in the Tax Scheme customer node, the scheme type was recomputed correctly depending on the companyID node. However, during the fix, a condition was wrongly introduced. This will lead to some issue: when a customer has no VAT, he should be given the default VAT. However, due to condition, the customer gets given the Default VAT only when he does not have a vat NOR A COMPANY REGISTRY. Solution --------- Remove the condition no-task --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#252475
This update ensures that the 'Insert in spreadsheet' action is only visible to users with the necessary permissions for Documents and Dashboards. Previously, users without these permissions could still see the action, which has now been corrected for a more streamlined and secure user experience.
Original PR description
Current behavior before PR: - The 'Insert in spreadsheet' action was always visible in the list view action menu, even when the user lacked access rights for Documents or Dashboards. Desired behavior after PR is merged: - The action is shown in the list view action menu only if the user has the required permissions. Task: 5930184 Forward-Port-Of: odoo/enterprise#109739 Forward-Port-Of: odoo/enterprise#108099
This update ensures that users only see the 'Insert in spreadsheet' option in the kanban view if they have the necessary permissions. Previously, users without these permissions could still see the option, leading to potential confusion. The update also removes a restriction that prevented inserting records from kanban views grouped by m2m fields, streamlining the process.
Original PR description
Current behavior before PR: - The 'Insert in spreadsheet' action was always visible in the kanban view action menu, even when the user lacked access rights for Documents or Dashboards. - Inserting records from a kanban view into a spreadsheet was blocked when the view was grouped by an m2m field. Desired behavior after PR is merged: - The action is shown in the kanban view action menu only if the user has the required permissions. - The m2m field check is removed when inserting from kanban views. Task: 5930184 Forward-Port-Of: odoo/enterprise#108098
This update allows all agents with live chat access to edit the description of a live chat conversation, regardless of whether they are a member of the channel. Previously, only channel members could make these changes. This improves agent flexibility and efficiency in managing live chat interactions.
Original PR description
…cription **Before this PR**, only users who were channel members could edit the description of a live chat conversation. With this change, agents who have live chat access can now edit the channel description **even if they are not members** of that specific live chat channel. task-5046015 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#251451
This update resolves an issue that occurred when the demo version of Odoo Enterprise was used. Specifically, certain buttons were incorrectly triggered, causing unexpected behavior within the accounting module. This fix ensures the demo mode functions reliably and prevents potential disruptions for users.
Original PR description
community https://github.com/odoo/enterprise/pull/97209 Forward-Port-Of: odoo/enterprise#109792
4 changes
Enhancements to existing features
This update enhances the demo data loading process in Odoo by ensuring the system accurately reflects demo module states and automatically installs demo modules. Previously, demo data didn't always update the system's state correctly. Now, the demo data loading is more reliable and consistent, providing a better starting point for users.
Original PR description
[IMP] core: improve force demo Improve the force demo function 1. update registry when demo data triggered module state changes 2. add ``install_demo`` to the context when loading demo data enterprise https://github.com/odoo/enterprise/pull/109792 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#250868
Resolved issues and error corrections
This update ensures that the 'Insert in spreadsheet' action is only visible to users with the necessary permissions for Documents and Dashboards. Previously, users without these permissions could still see the action, which has now been corrected for a more streamlined and secure user experience.
Original PR description
Current behavior before PR: - The 'Insert in spreadsheet' action was always visible in the list view action menu, even when the user lacked access rights for Documents or Dashboards. Desired behavior after PR is merged: - The action is shown in the list view action menu only if the user has the required permissions. Task: 5930184 Forward-Port-Of: odoo/enterprise#109739 Forward-Port-Of: odoo/enterprise#108099
This update resolves an issue that occurred when the demo version of Odoo Enterprise was used. Specifically, certain buttons were being triggered unnecessarily, causing unexpected behavior in the accounting module. This change ensures a smoother and more reliable experience for users in demo mode.
Original PR description
community https://github.com/odoo/enterprise/pull/97209 Forward-Port-Of: odoo/enterprise#109792
This update corrects a bug that prevented the system from accepting valid GSTINs for Non-Resident Indian (NRI) taxpayers. The previous validation rule was too restrictive, rejecting numbers that followed a different format. This change ensures accurate tax ID processing for NRI customers.
Original PR description
Currently, valid GSTINs for certain Non-Resident taxpayers are rejected. **Steps to reproduce:** - Install the `l10n_in` module. - Navigate to Settings > Users & Companies > Companies. - Open `IN…
Currently, valid GSTINs for certain Non-Resident taxpayers are rejected. **Steps to reproduce:** - Install the `l10n_in` module. - Navigate to Settings > Users & Companies > Companies. - Open `IN Company` and set `Tax ID` to `9922JPN29001OSU` and try to `save`. **Error:** `The VAT number [9922JPN29001OSU] for partner [IN Company] does not seem to be valid.` `Note: the expected format is 12AAAAA1234AAZA` The system rejects the GSTIN, although it is valid and verifiable on the official GST portal: https://services.gst.gov.in/services/searchtp **Root cause:** At [2], the GSTIN validation regex for NRI taxpayers only supports formats ending with `NRX` (X = any alphanumeric character). However, certain valid GSTINs follow a different structure and are not matched by the existing regex. **Fix:** This commit ensures that valid NRI GSTIN formats are accepted during validation. Confirm with IN PO. [1]: https://services.gst.gov.in/services/searchtp [2]: https://github.com/odoo/odoo/blob/5e59f4b3def44aa84c06ba4c2ed34bf2e8da928f/addons/base_vat/models/res_partner.py#L712-L723 opw-5956299 Forward-Port-Of: odoo/odoo#252647 Forward-Port-Of: odoo/odoo#251760
2 changes
Resolved issues and error corrections
This update ensures that the 'Insert in spreadsheet' action is only visible to users with the necessary permissions for Documents and Dashboards. Previously, users without these permissions could still see the action, which has now been corrected to enhance security and streamline the user experience.
Original PR description
Current behavior before PR: - The 'Insert in spreadsheet' action was always visible in the list view action menu, even when the user lacked access rights for Documents or Dashboards. Desired behavior after PR is merged: - The action is shown in the list view action menu only if the user has the required permissions. Task: 5930184 Forward-Port-Of: odoo/enterprise#109739 Forward-Port-Of: odoo/enterprise#108099
This update fixes a printing issue that occurred when creating duplicate vendor bills using DIAN support documents. The fix ensures that the report template only attempts to print related information when a valid DIAN attachment exists, preventing a crash caused by parsing errors.
Original PR description
**Steps to reproduce:** * Install the **l10n_co_dian** module. * Enable DIAN 2.1 operation mode: **Support Documents** in settings. * Create a vendor bill using a **DIAN support document** journal. * Confirm the vendor bill. * Click **Print**. **Observed behavior:** * Printing fails with `ValueError: can only parse strings`. **Cause:** * The report template unconditionally called `_l10n_co_dian_get_extra_invoice_report_values()`, which parses `l10n_co_dian_attachment_id.raw` via `etree.fromstring()`. * On duplicated bills, `l10n_co_dian_document_ids` (and thus the computed `l10n_co_dian_attachment_id`) is empty, so `.raw` is `False`. **Fix:** * Wrap the QR code / CUFE / signing section in the report template with `t-if='o.l10n_co_dian_attachment_id'` so it is only rendered when the DIAN attachment exists. opw-5930173 Forward-Port-Of: odoo/enterprise#108645
3 changes
Resolved issues and error corrections
This update ensures that the 'Insert in spreadsheet' action is only visible to users with the necessary permissions for Documents and Dashboards. Previously, users without these permissions could still see the action, which has now been corrected for a more streamlined and secure user experience.
Original PR description
Current behavior before PR: - The 'Insert in spreadsheet' action was always visible in the list view action menu, even when the user lacked access rights for Documents or Dashboards. Desired behavior after PR is merged: - The action is shown in the list view action menu only if the user has the required permissions. Task: 5930184 Forward-Port-Of: odoo/enterprise#109739 Forward-Port-Of: odoo/enterprise#108099
This update fixes an issue where the system incorrectly rejected valid Non-Resident Indian (NRI) GSTINs. The change adjusts the validation process to accept a wider range of valid GSTIN formats, ensuring accurate tax ID input for NRI company records. This prevents errors and improves data integrity.
Original PR description
Currently, valid GSTINs for certain Non-Resident taxpayers are rejected. **Steps to reproduce:** - Install the `l10n_in` module. - Navigate to Settings > Users & Companies > Companies. - Open `IN…
Currently, valid GSTINs for certain Non-Resident taxpayers are rejected. **Steps to reproduce:** - Install the `l10n_in` module. - Navigate to Settings > Users & Companies > Companies. - Open `IN Company` and set `Tax ID` to `9922JPN29001OSU` and try to `save`. **Error:** `The VAT number [9922JPN29001OSU] for partner [IN Company] does not seem to be valid.` `Note: the expected format is 12AAAAA1234AAZA` The system rejects the GSTIN, although it is valid and verifiable on the official GST portal: https://services.gst.gov.in/services/searchtp **Root cause:** At [2], the GSTIN validation regex for NRI taxpayers only supports formats ending with `NRX` (X = any alphanumeric character). However, certain valid GSTINs follow a different structure and are not matched by the existing regex. **Fix:** This commit ensures that valid NRI GSTIN formats are accepted during validation. Confirm with IN PO. [1]: https://services.gst.gov.in/services/searchtp [2]: https://github.com/odoo/odoo/blob/5e59f4b3def44aa84c06ba4c2ed34bf2e8da928f/addons/base_vat/models/res_partner.py#L712-L723 opw-5956299 Forward-Port-Of: odoo/odoo#252540 Forward-Port-Of: odoo/odoo#251760
This update resolves a printing error that occurred when generating invoices with DIAN support documents. The fix prevents a crash caused by an attempt to print sections of the invoice when the necessary DIAN attachment wasn't available. This ensures invoices with multiple support documents can be printed correctly.
Original PR description
**Steps to reproduce:** * Install the **l10n_co_dian** module. * Enable DIAN 2.1 operation mode: **Support Documents** in settings. * Create a vendor bill using a **DIAN support document** journal. * Confirm the vendor bill. * Click **Print**. **Observed behavior:** * Printing fails with `ValueError: can only parse strings`. **Cause:** * The report template unconditionally called `_l10n_co_dian_get_extra_invoice_report_values()`, which parses `l10n_co_dian_attachment_id.raw` via `etree.fromstring()`. * On duplicated bills, `l10n_co_dian_document_ids` (and thus the computed `l10n_co_dian_attachment_id`) is empty, so `.raw` is `False`. **Fix:** * Wrap the QR code / CUFE / signing section in the report template with `t-if='o.l10n_co_dian_attachment_id'` so it is only rendered when the DIAN attachment exists. opw-5930173 Forward-Port-Of: odoo/enterprise#108645
1 change
Resolved issues and error corrections
This update fixes a bug that caused printing of vendor bills using DIAN support documents to fail. The issue stemmed from a report template that incorrectly processed duplicate bills, leading to a parsing error. The fix ensures that printing only occurs when a valid DIAN attachment is present, improving printing reliability.
Original PR description
**Steps to reproduce:** * Install the **l10n_co_dian** module. * Enable DIAN 2.1 operation mode: **Support Documents** in settings. * Create a vendor bill using a **DIAN support document** journal. * Confirm the vendor bill. * Click **Print**. **Observed behavior:** * Printing fails with `ValueError: can only parse strings`. **Cause:** * The report template unconditionally called `_l10n_co_dian_get_extra_invoice_report_values()`, which parses `l10n_co_dian_attachment_id.raw` via `etree.fromstring()`. * On duplicated bills, `l10n_co_dian_document_ids` (and thus the computed `l10n_co_dian_attachment_id`) is empty, so `.raw` is `False`. **Fix:** * Wrap the QR code / CUFE / signing section in the report template with `t-if='o.l10n_co_dian_attachment_id'` so it is only rendered when the DIAN attachment exists. opw-5930173 Forward-Port-Of: odoo/enterprise#108645
8 changes
Resolved issues and error corrections
This update removes a display field ('Visible Internally Only') from the customer rating form in the Helpdesk module. This field was no longer needed as customer ratings are no longer visible on the website. This cleanup improves the user experience and reduces unnecessary complexity.
Original PR description
**Steps to reproduce:** - Open a Helpdesk ticket with a customer rating. - View the rating form. - Observe the field ‘Visible Internally Only’ still showing. **Issue:** - The field is displayed even though ratings are no longer shown on the website. **Reason:** - The field is now irrelevant but still present in the view. **Fix:** - Invisible the ‘Visible Internally Only’ field from the customer rating form in the affected version. **Task id - 5359052** Forward-Port-Of: odoo/enterprise#109287 Forward-Port-Of: odoo/enterprise#100686
This update corrects a visual issue where the unit display (hours/days) for KPIs in the sale timesheet was misaligned. The change restores the original layout, ensuring accurate and consistent KPI reporting. This resolves a minor display problem impacting user readability.
Original PR description
Due to the recent refactoring of the `formatFloatTime` formatter in odoo/enterprise#108072, the KPIs lost their layout, resulting in a misaligned display. This commit restores the original layour for the KPI header, ensuring the unit (hours/days) is correctly shown next to the value. Forward-Port-Of: odoo/enterprise#109809
This update removes unnecessary debugging code that was inadvertently included in account reports. Previously, this code was being sent to the JavaScript interface, causing potential issues with report data. This change ensures cleaner report data and a more stable user experience.
Original PR description
Since this commit https://github.com/odoo/enterprise/commit/265629249ec71797b6387b46d2245154159b0c00 the code has been returned in the report information, therefore the 'code' key is present in the JSON sent to the JS. no-task <img width="884" height="676" alt="image" src="https://github.com/user-attachments/assets/1f22cc29-2d3d-4c61-9380-e1de77543339" />
This update addresses a technical issue where discussion counters and comments weren't being properly updated after recent improvements to the Odoo Enterprise platform. The fix ensures accurate tracking of discussion activity, improving the overall functionality of the discussion module.
Original PR description
The file was not updated following recent improvements. https://github.com/odoo/odoo/pull/252508
This update resolves an issue where tags in German financial reports were incorrectly sorted, causing problems with the auto-complete feature. The fix ensures tags are properly ordered, improving the user experience and report accuracy. Additional tests have been added to prevent similar issues in the future.
Original PR description
Commit https://github.com/odoo/odoo/commit/db0d499952192ede0def2a070e103ba67952387c inverted some tags which is wrong Tags must be sorted for the auto complete to work properly Improving tests to catch more errors opw-5415426 Forward-Port-Of: odoo/enterprise#108848
This update resolves an issue where users received empty deprecation schedule reports if customer customizations to their accounting records caused conflicts with Odoo's internal calculations. The fix ensures accurate report generation by granting administrative access, guaranteeing correct data retrieval for asset depreciation schedules.
Original PR description
Following odoo/enterprise@ece0405785, in case a customer modified the `account.move.line` record rules in a way which is incompatible with the AML shadowing, user will only get an empty deprecation schedule report. This commit as a sudo, to ensure we get a correct report, access rights being already check for `account.asset` records. Forward-Port-Of: odoo/enterprise#108901
This update refines how Odoo handles binary files (like invoices or statements) by ensuring they are consistently represented as `BinaryValue` objects. This change improves data integrity and compatibility across various Odoo modules, particularly those dealing with financial reporting and document imports. It's a standard best practice for data type consistency.
Original PR description
https://github.com/odoo/odoo/pull/244421
This update resolves a problem that occurred when the demo version of Odoo Enterprise was used. Specifically, certain buttons were triggered unexpectedly, causing disruptions. This change ensures the demo mode functions correctly, providing a stable and reliable experience for testing and evaluation.
Original PR description
community https://github.com/odoo/enterprise/pull/97209 Forward-Port-Of: odoo/enterprise#109792
1 change
Resolved issues and error corrections
This update fixes a bug that caused printing of vendor bills using DIAN support documents to fail. The issue stemmed from a report template that incorrectly processed duplicate bills, leading to a parsing error. The fix ensures that printing only occurs when a valid DIAN attachment exists, improving printing reliability.
Original PR description
**Steps to reproduce:** * Install the **l10n_co_dian** module. * Enable DIAN 2.1 operation mode: **Support Documents** in settings. * Create a vendor bill using a **DIAN support document** journal. * Confirm the vendor bill. * Click **Print**. **Observed behavior:** * Printing fails with `ValueError: can only parse strings`. **Cause:** * The report template unconditionally called `_l10n_co_dian_get_extra_invoice_report_values()`, which parses `l10n_co_dian_attachment_id.raw` via `etree.fromstring()`. * On duplicated bills, `l10n_co_dian_document_ids` (and thus the computed `l10n_co_dian_attachment_id`) is empty, so `.raw` is `False`. **Fix:** * Wrap the QR code / CUFE / signing section in the report template with `t-if='o.l10n_co_dian_attachment_id'` so it is only rendered when the DIAN attachment exists. opw-5930173 Forward-Port-Of: odoo/enterprise#108645