Odoo Changelog — 2025-10-02

Thursday, October 2, 2025

2 changes · 17.0

Improvements(2)

Enhancements to existing features

[IMP] l10n_br_avatax: change label from Mercosul NCM to LC116 for services

Enterprise17.0l10n_br_avatax

Brazilian service products now show the correct LC116 Code label instead of the Mercosul NCM Code label. This reduces confusion when configuring fiscal information because goods and services use different naming conventions for their tax classification codes.

Original PR description

Purpose:-
- In Brazil, NCM is a code that has an acronym to specify the Mercosul Common
Name for products, and for services, the right name is LC116 (Complementary Law
116), which specifies the federal code for a service.
- But we have the same field `l10n_br_ncm_code_id` to configure both NCM for
goods and  LC116 for services and the same table can be used for both the cases.
- So while configuring fiscal information for a service, user don't understand
why it still shows the NCM label instead of LC116.

Before this commit:-
- Label `Mercosul NCM Code` was displayed for services confusing users.

After this commit:-
- Label `Mercosul NCM Code` is replaced with `LC116 Code` only for services.
- Tooltip is also improved for better understanding.

task-5096435

#brazil#localization#tax#services

[IMP] web: Add context support to the name_search call in many2many_checkboxes

PR #215420

Core17.0web

This update lets checkbox-based multi-select fields use the same custom search settings as other parts of the system. It improves consistency and supports business cases where records must be filtered or handled differently based on context, such as attachments.

Original PR description

**Description of the issue/feature this PR addresses:**
When `name_search` is called, the `context` is not passed to the method. In some cases, this is necessary, for example, if the field is related to `ir.attachment` and you want to pass `skip_res_field_check` in the context (see https://github.com/OCA/social/pull/1672).

**Current behavior before PR:**
The `context` is not passed to `name_search`.

**Desired behavior after PR is merged:**

Ability to pass context to name_search.

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

TT56840
@Tecnativa @pedrobaeza

#many2many#search#context#checkboxes

Purpose:- - In Brazil, NCM is a code that has an acronym to specify the Mercosul Common Name for products, and for services, the right name is LC116 (Complementary Law 116), which specifies the federal code for a service. - But we have the same field `l10n_br_ncm_code_id` to configure both NCM for goods and LC116 for services and the same table can be used for both the cases. - So while configuring fiscal information for a service, user don't understand why it still shows the NCM label instead of LC116. Before this commit:- - Label `Mercosul NCM Code` was displayed for services confusing users. After this commit:- - Label `Mercosul NCM Code` is replaced with `LC116 Code` only for services. - Tooltip is also improved for better understanding. task-5096435

**Description of the issue/feature this PR addresses:** When `name_search` is called, the `context` is not passed to the method. In some cases, this is necessary, for example, if the field is related to `ir.attachment` and you want to pass `skip_res_field_check` in the context (see https://github.com/OCA/social/pull/1672). **Current behavior before PR:** The `context` is not passed to `name_search`. **Desired behavior after PR is merged:** Ability to pass context to name_search. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr TT56840 @Tecnativa @pedrobaeza