Skip to Content
Odoo model

nemhandel.response

Business Level Responses for Nemhandel. Defined in module l10n_dk; exists in Odoo 18, 19, 20. Across the upgrade steps we tracked: 0 fields added, 0 removed, 0 renamed.

  1. Odoo 16 not present
  2. Odoo 17 not present
  3. Odoo 18 l10n_dk_nemhandel_response
  4. Odoo 19 l10n_dk_nemhandel_response
  5. Odoo 20 l10n_dk

Odoo 17 to 18

Community only All changes in this step

New model in Odoo 18.

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
2 views of this model removed
  • l10n_dk_nemhandel_response.nemhandel_response_view_form
  • l10n_dk_nemhandel_response.nemhandel_response_view_list

All fields declared on nemhandel.response (5)

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 5 fields
FieldTypeLabelModule1617181920
company_idmany2onel10n_dk
move_idmany2one account.movel10n_dk
nemhandel_message_uuidcharNemhandel UUIDl10n_dk
nemhandel_stateselectionNemhandel statusl10n_dk
response_codeselectionl10n_dk

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.