Odoo Changelog — 2024-01-17

Wednesday, January 17, 2024

28 changes · master

Other(3)

Miscellaneous changes

[FW][FIX] account_intrastat{_expiry}: add new commodity codes

Enterprisemaster

From the 1st of January 2024, commodity code [0803 90 10] is replaced by these 2 new codes: - [0803 90 11] Plátano de Canarias - [0803 90 19] Others Source: https://www.nbb.be/en/statistics/foreign-trade/nomenclature-and-codes ![intrastat_new_codes](https://github.com/odoo/enterprise/assets/3715017/2e687d90-de55-463a-8b1f-bc5ac9938f36) opw-3676899 Forward-Port-Of: odoo/enterprise#54359 Forward-Port-Of: odoo/enterprise#54102

Original PR description

From the 1st of January 2024, commodity code [0803 90 10] is replaced by these 2 new codes:
- [0803 90 11] Plátano de Canarias
- [0803 90 19] Others

Source: https://www.nbb.be/en/statistics/foreign-trade/nomenclature-and-codes

![intrastat_new_codes](https://github.com/odoo/enterprise/assets/3715017/2e687d90-de55-463a-8b1f-bc5ac9938f36)

opw-3676899

Forward-Port-Of: odoo/enterprise#54359
Forward-Port-Of: odoo/enterprise#54102

[FW][FIX] {account_invoice/hr_expense}_extract: Fix auto-extraction of attachments.

PR #54482

Enterprisemaster

Original PR description

Problem --------- In the commit [24345812cb015e86f362f8c35176646239bfb803](https://github.com/odoo/odoo/commit/24345812cb015e86f362f8c35176646239bfb803) (odoo), we modified the extraction of…

Problem
---------
In the commit [24345812cb015e86f362f8c35176646239bfb803](https://github.com/odoo/odoo/commit/24345812cb015e86f362f8c35176646239bfb803) (odoo), we modified the extraction of attachment in such a way that mails coming in a journal from aliases with several attachments create several invoices.
Due to the urgency of the task, the computation of whether an attachment needs auto-extraction or not, has been skipped. This commit fixes this.

The problem of the failing test came from the conditional order that verified if the auto-extraction was needed or not. Here is the difference

What the test expected              
1. From alias                       
    a. Attachment is PDF            
2. New move or purchase document

What we had
1. New move
2. From alias
    a. Attachment is PDF
3. Purchase document

So, new documents were always extracted even though the option for extracting PDF only was active. Since all document created through a mail from a mail alias are new document, all attachments (no matter if binary or PDF) were extracted.

Solution
---------
Update the `_needs_auto_extract` and decoder to behave as the test expects; by shifting the conditions around. Also context key checks in both the `_needs_auto_extract` method and decoder to completely disable the calls to the OCR when needed.

Forward-Port-Of: odoo/enterprise#49816

[FW][FIX] account_reports: Journal Report Analytic Groupby bugged

PR #54476

Enterprisemaster

Original PR description

Descritpion of the issue/feature this commit addresses:

At the moment, trying to use the analytic groupy on the Journal Report results in a traceback. It is not possible to use it at all.

---

Steps to reproduce:

1-Activate the Analytic Accounting in the settings 
2-Activate the Analytic Groupby in the Journal Report's options 
3-Go to the Journal Report and apply any Analytic Groupby filter 
4-A traceback shows up

---

Desired behavior after this commit is merged:

This commit handles the issue by adding a check at the very start of the custom handler of the Journal Report. This new check verifies that no analytic groupby filter is being applied on the report. If it is the case, an error is raised to tell the user the feature is not supported by that report.

While at it, the Horizontal Grouping and Period Comparison options have also been disabled because their rendering was making the report unreadable and they added no value to it.

With this commit, the Journal Report can't use Analytic Groupby, Horizontal Grouping or Period Comparison.

---

task-3600349

Forward-Port-Of: odoo/enterprise#53807

Rows:Rows per page:

10 25 50 100

2 / 2Page 2 of 2 · 28 days total

Problem --------- In the commit [24345812cb015e86f362f8c35176646239bfb803](https://github.com/odoo/odoo/commit/24345812cb015e86f362f8c35176646239bfb803) (odoo), we modified the extraction of attachment in such a way that mails coming in a journal from aliases with several attachments create several invoices. Due to the urgency of the task, the computation of whether an attachment needs auto-extraction or not, has been skipped. This commit fixes this. The problem of the failing test came from the conditional order that verified if the auto-extraction was needed or not. Here is the difference What the test expected 1. From alias a. Attachment is PDF 2. New move or purchase document What we had 1. New move 2. From alias a. Attachment is PDF 3. Purchase document So, new documents were always extracted even though the option for extracting PDF only was active. Since all document created through a mail from a mail alias are new document, all attachments (no matter if binary or PDF) were extracted. Solution --------- Update the `_needs_auto_extract` and decoder to behave as the test expects; by shifting the conditions around. Also context key checks in both the `_needs_auto_extract` method and decoder to completely disable the calls to the OCR when needed. Forward-Port-Of: odoo/enterprise#49816

Descritpion of the issue/feature this commit addresses: At the moment, trying to use the analytic groupy on the Journal Report results in a traceback. It is not possible to use it at all. --- Steps to reproduce: 1-Activate the Analytic Accounting in the settings 2-Activate the Analytic Groupby in the Journal Report's options 3-Go to the Journal Report and apply any Analytic Groupby filter 4-A traceback shows up --- Desired behavior after this commit is merged: This commit handles the issue by adding a check at the very start of the custom handler of the Journal Report. This new check verifies that no analytic groupby filter is being applied on the report. If it is the case, an error is raised to tell the user the feature is not supported by that report. While at it, the Horizontal Grouping and Period Comparison options have also been disabled because their rendering was making the report unreadable and they added no value to it. With this commit, the Journal Report can't use Analytic Groupby, Horizontal Grouping or Period Comparison. --- task-3600349 Forward-Port-Of: odoo/enterprise#53807