Saturday, August 22, 2026
1 change · saas-19.4
Enhancements to existing features
This update simplifies how localization-specific partner identifiers are made available across Odoo. It reduces duplicate setup work for teams adding country-specific identifier rules, while keeping core tax identifier metadata available consistently.
Original PR description
When adding an l10n-only identifier metadata, you'll want to EXTENDS the `_get_all_additional_identifiers_metadata` if you want your new identifier to be displayed on the JSON additional identifiers. Before this commit, you also needed to EXTENDS `_get_all_identifiers_metadata` to make it available to globally, regardless of if it was in additional_identifers or not, for example for validation purposes, which is tedious and easy to avoid. Note that it make sense that the TIN_METADATA are always added in base module, since they describe the content of the `vat` field that is generic, and that we want to be available for all databases, regardless of which localization is installed. task-none