Odoo model
sale.edi.xml.ubl_bis3
Sale BIS Ordering 3.5. Defined in module sale_edi_ubl; exists in Odoo 18, 19, 20. Across the upgrade steps we tracked: 0 fields added, 0 removed, 0 renamed.
- Odoo 16 not present
- Odoo 17 not present
- Odoo 18 sale_edi_ubl
- Odoo 19 sale_edi_ubl
- Odoo 20 sale_edi_ubl
New model in Odoo 18.
No longer inherits sale.edi.common.
No change to this model's own fields in this step.
All fields declared on sale.edi.xml.ubl_bis3 (0)
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 0 fields
| Field | Type | Label | Module | 16 | 17 | 18 | 19 | 20 |
|---|
Related models
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