Odoo model

l10n_vn_edi_viettel.cancellation

E-invoice cancellation wizard. Defined in module l10n_vn_edi_viettel; exists in Odoo 17, 18, 19. Across the upgrade steps we tracked: 0 fields added, 0 removed, 0 renamed.

Odoo 16 not present
Odoo 17 l10n_vn_edi_viettel
Odoo 18 l10n_vn_edi_viettel
Odoo 19 l10n_vn_edi_viettel
Odoo 20 not present

Odoo 16 to 17

Community only All changes in this step

New model in Odoo 17.

Odoo 17 to 18

Community only All changes in this step

No change to this model's own fields in this step.

Odoo 18 to 19

Community + Enterprise All changes in this step

No change to this model's own fields in this step.

Odoo 19 to 20

Community + Enterprise All changes in this step

Removed in Odoo 20.

1 views of this model removed

l10n_vn_edi_viettel.l10n_vn_edi_cancellation_form

All fields declared on l10n_vn_edi_viettel.cancellation (4)

Fields this model declares itself in any version, with the versions they exist in. Inherited fields (mail.thread and other mixins) are on the parent model's page.

present not present not covered (Enterprise, Odoo 16 and 17)

Show all 4 fields

Field	Type	Label	Module
agreement_document_date	datetime	Agreement Date	l10n_vn_edi_viettel
agreement_document_name	char	Agreement Name	l10n_vn_edi_viettel
invoice_id	many2one account.move	Invoice to cancel	l10n_vn_edi_viettel
reason	char	Reason	l10n_vn_edi_viettel

Related models

Linked by its relational fields: account.move

Coverage. Odoo 16 to 17 and 17 to 18 compare Community modules only (the Enterprise 16 and 17 sources are not available to us). Odoo 18 to 19 and 19 to 20 include Community and Enterprise modules. Everything here comes from a static read of the Odoo source code: a field counts as removed only when no parent model, mixin or delegated model still provides it. Fields created dynamically at run time can be missed, and entries we could not confirm are marked as low confidence.

Planning an Odoo upgrade?

Odoo app Check your own database: Studio Upgrade Checker Scans your Studio fields, views, automations and custom code for everything listed here before you upgrade. See it on the Odoo Apps store Odoo app Fix broken views: Studio View Repair Assistant Finds views that stopped loading after an upgrade and helps you repair the xpaths and fields they point at. See it on the Odoo Apps store Upgrade service Need the upgrade done? Book a call We move databases between major Odoo versions, port custom modules and validate the data. Book a call Free Free upgrade scan, we run it for you Send us a copy of your database or give us access and we report what will break on the target version. Ask for a scan