Skip to Content
Odoo model

sale.order.cancel

Sales Order Cancel. Defined in module sale; exists in Odoo 16, 17, 18. Across the upgrade steps we tracked: 0 fields added, 1 removed, 0 renamed.

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

Odoo 16 to 17

Community only All changes in this step

Fields removed (1)

FieldTypeModuleNotes
email_fromcharsale

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

Removed in Odoo 19.

3 views of this model removed
  • sale.sale_order_cancel_view_form
  • sale_purchase.sale_order_cancel_view_form
  • sale_stock.sale_order_cancel_view_form_inherit

All fields declared on sale.order.cancel (7)

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 7 fields
FieldTypeLabelModule1617181920
author_idmany2one res.partnerAuthorsale
display_delivery_alertbooleanDelivery Alertsale_stock
display_invoice_alertbooleanInvoice Alertsale
display_purchase_orders_alertbooleanPurchase Order Alertsale_purchase
email_fromcharFromsale
order_idmany2one sale.orderSale Ordersale
recipient_idsmany2many res.partnerRecipientssale

Related models

Inherits: mail.composer.mixin

Linked by its relational fields: res.partnersale.order

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.