Skip to Content
Odoo model · Enterprise

ai.embedding

Attachment Chunks Embedding. Defined in module ai; exists in Odoo 19, 20. Across the upgrade steps we tracked: 3 fields added, 2 removed, 0 renamed, 1 type changes.

Stores vector embeddings for document chunks. Used to perform semantic searches to find relevant context for user queries.

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

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 18 to 19

Community + Enterprise All changes in this step

New model in Odoo 19.

Odoo 19 to 20

Community + Enterprise All changes in this step

Fields removed (2)

FieldTypeModuleNotes
attachment_idmany2oneai
checksumcharai

Fields added (3)

FieldTypeModule
embedding_errorcharai
res_idmany2one_referenceai
res_modelcharai

Type changed (1)

FieldOdoo 19Odoo 20
embedding_model selectionchar

All fields declared on ai.embedding (9)

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 9 fields
FieldTypeLabelModule1617181920
attachment_idmany2one ir.attachmentAttachmentaiE
checksumcharaiE
contenttextChunk ContentaiE
embedding_errorcharEmbedding erroraiE
embedding_modelcharEmbedding ModelaiE
has_embedding_generation_failedbooleanHas Embedding Generation FailedaiE
res_idmany2one_referenceThe ID of a linked record.aiE
res_modelcharThe model of a linked recordaiE
sequenceintegerSequenceaiE

Related models

Linked by its relational fields: ir.attachment

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.