Technical module for the EDI suite to provide a way to store some technical data.
For instance, you receive a sale order via EDI and you want to store some original values from the incoming file without having to parse again the whole file or compute values that you need later to compite something else.
Important
This is an alpha version, the data model and design can change at any time without warning. Only for development or testing purpose, do not use in production. More details on development status
Table of contents
On a edi.exchange.record:
exc_record.set_metadata({...}) exc_record.get_metadata()
- Make sure your model inherits from edi.exchange.consumer.mixin
- Override _edi_get_metadata_to_store
NOTE: automatic storage happens only when create gets called in an EDI framework session (edi_framework_action is in ctx).
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
- Camptocamp
- Simone Orsi <[email protected]>
- Duong (Tran Quoc) <[email protected]>
The migration of this module from 14.0 to 16.0 was financially supported by Camptocamp.
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
Current maintainer:
This module is part of the OCA/edi-framework project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.