Skip to Content
Odoo model · Enterprise

l10n_co.exogenous.config

Colombian Exogenous Report Mapping. Defined in module l10n_co_reports; exists in Odoo 20. Across the upgrade steps we tracked: 0 fields added, 0 removed, 0 renamed.

  1. Odoo 16 not covered
  2. Odoo 17 not covered
  3. Odoo 18 not present
  4. Odoo 19 not present
  5. Odoo 20 l10n_co_reports

This is an Enterprise model: Odoo 16 and 17 Enterprise sources are not part of the data, so those versions show as not covered.

Odoo 19 to 20

Community + Enterprise All changes in this step

New model in Odoo 20.

All fields declared on l10n_co.exogenous.config (8)

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 8 fields
FieldTypeLabelModule1617181920
account_idsmany2many account.accountl10n_co_reportsE
allowed_account_idsmany2many account.accountl10n_co_reportsE
category_sequenceintegerl10n_co_reportsE
conceptcharConceptl10n_co_reportsE
exogenous_category_idmany2one l10n_co.exogenous.categoryCategoryl10n_co_reportsE
report_typeselectionReportl10n_co_reportsE
show_conceptbooleanl10n_co_reportsE
value_to_reportselectionValue to Reportl10n_co_reportsE

Related models

Linked by its relational fields: account.accountl10n_co.exogenous.category

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.