You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The stupid guy who migrated l10n_fr_siret to v16 (me !) didn't spot that the field company_registry was added by Odoo SA in the base module, cf https://github.com/odoo/odoo/blob/16.0/odoo/addons/base/models/res_partner.py#L225
This field is used to store the national company identification number, cf for example the code of l10n_be and l10n_ro (they auto-extract it from the VAT number).
From my understanding, the field company_registry of l10n_fr was designed to write the name of the RCS where the company was registered. For example, for Akretion France which is RCS Lyon 792377731, then company_registry would store "Lyon". I don't use that field myself, and I don't find it useful. l10n_fr_siret was ported to v16 one year ago, and nobody found the bug yet... so I guess that I'm not the only one who don't use that field !!!
2 options:
remove company registry in l10n_fr_siret because we think that it's not useful
rename the field: for example fr_company_registry
I vote for option 1.
The text was updated successfully, but these errors were encountered:
The stupid guy who migrated l10n_fr_siret to v16 (me !) didn't spot that the field company_registry was added by Odoo SA in the base module, cf https://github.com/odoo/odoo/blob/16.0/odoo/addons/base/models/res_partner.py#L225
This field is used to store the national company identification number, cf for example the code of l10n_be and l10n_ro (they auto-extract it from the VAT number).
From my understanding, the field company_registry of l10n_fr was designed to write the name of the RCS where the company was registered. For example, for Akretion France which is RCS Lyon 792377731, then company_registry would store "Lyon". I don't use that field myself, and I don't find it useful. l10n_fr_siret was ported to v16 one year ago, and nobody found the bug yet... so I guess that I'm not the only one who don't use that field !!!
2 options:
I vote for option 1.
The text was updated successfully, but these errors were encountered: