Allow to store metadata for related records.
auto_awesome What this module does
AI-generated from the code · Odoo 19.0Stores technical metadata on EDI exchange records and shows it in a Metadata tab on the EDI record form. Metadata can be set and read programmatically by other EDI modules.
This module extends the EDI framework so that each EDI exchange record can carry extra technical information, stored as JSON-like data. On the EDI exchange record form, a new "Metadata" tab appears after the related records section, but only when there is metadata to show and only for users with the technical/debug access group.
The metadata is displayed as formatted text so it can be inspected easily. The module also adds helper methods that other EDI modules can call to write metadata onto an exchange record or read it back.
When records that consume EDI exchanges are created, the module checks whether the creation is happening as part of an EDI action. If so, and if the values include a reference to the originating exchange record, it can store metadata on that exchange record before the new record is created. Which values are stored is decided by a hook method that other modules can override; by default nothing extra is stored.
In short, this module does not add business rules or user-facing workflows on its own. It provides the storage, display and programming interface that other EDI modules use to attach and retrieve technical metadata on edi.exchange.record and on exchange consumers.
Depends on
Required by other modules
Models and fields (2)
- edi.exchange.record · extends an existing modelmetadata, metadata_display
- edi.exchange.consumer.mixin · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 19.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 5 confirmed, 4 with no information of 9 versions.
Sources · Odoo 19.0
Confirmed on 2026-11-03 in branch 19.0 of OCA/edi-framework.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.