Language Code Error In odoo19 , when Migrate a module from version 18 to Version 19

Question

Invalid language code: ${object.employee_id.partner_id.lang},

How Can i Solve this I tried this way also,

<field name="lang">{{object.employee_id.partner_id.lang}}</field>

odoo.tools.convert.ParseError: while parsing file:/e:/odoo19e/custom/payroll-custom/vkd_employee_resignation/data/mail_templates.xml:3

Oops! We couldn't save your template due to an issue with this value: {{object.employee_id.partner_id.lang}}. Correct it and try again.

But there is a error too, Can Someone Help me to solve this??

Ramiz Belim · Answer

Hello,
The error occurs because partner_id.lang is not always considered a valid language code at the mail template rendering stage, and sometimes Odoo validation fails when accessing nested fields this way inside <field name="lang">.

Instead, you should directly use the employee language field, which is already validated by Odoo. This approach is also used in Odoo Enterprise:

<field name="lang">{{ object.employee_id.lang }}</field>

Pavan · Answer

*In Odoo 19, language codes must follow the strict ISO format ll_CC.*
If your module from Odoo 18 includes old or custom codes like en_UK, en_in, fr_BE@euro, or any non-standard code, Odoo 19 will raise a /Language Code Error/.
*Fix:*
Update all language codes in XML, demo data, and PO files to valid formats (e.g., en_GB, en_US, sw_KE, hi_IN).
Rename PO translation files accordingly.
Remove or clean invalid res.lang entries.
Once all codes follow xx_YY format, the module will install correctly i

Kunjan Patel · Answer

Hello Kalana Piyumantha,
I hope you are doing well

Simple Fix for Dynamic Lang in Odoo 19

1. Best Solution: Use partner_to field - Odoo auto-detects lang from partner

<field name="partner_to">{{object.employee_id.partner_id.id}}</field>

2. Or: Remove/leave lang field empty in your custom module override

I hope this information helps you

Thanks & Regards,
Kunjan Patel

Cybrosys Techno Solutions Pvt.Ltd · Answer

Hi,
That error usually means that the language data for your database (in res.lang) doesn’t match what v19 expects — Odoo prohibits changing language codes on upgrade via res.lang.csv, so the import fails.
To solve this:
Don’t attempt to modify existing language codes when migrating. Keep the original code values in res.lang.
If you need a new language, add it after the upgrade via Settings → Languages.
If the module provides custom translations, ensure their .po / .csv files use valid, consiste

Publicaciones relacionadas	Respuestas	Vistas
import error occurd when migrating from v18 to v19 .ImportError: cannot import name 'decimal_precision' from 'odoo.addons' (unknown location) Resuelto error import odoo18 odoo19	1 dic 25	1559
Error when sending email with template in Odoo 9 mail error templates template odoo9	2 oct 17	6389
Change User Mail Template mail templates	2 may 24	4825
odoo server error mail error	0 sept 23	3056
odoo 16 saas odoo18 odoo19	0 jul 23	6

Esta pregunta ha sido marcada

¿Le interesa esta conversación? ¡Participe en ella!