Technical module for the EDI suite module to retrieve data for parties of an exchange.
This module provides default component and a mixin to be used for registering new components for specific backends.
Deprecated: the actual party data lookup logic has moved to edi_party_helper_oca, which has no dependency on the component framework. This module now only wraps it in a component for backward compatibility and will be removed once its usages are ported over. A deprecation notice is logged on server startup while this module is installed.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Technical compatibility module that lets EDI backends retrieve party (partner) information for an exchange through a component. It is deprecated: the real logic now lives in the party helper module.
This module is a technical bridge for the EDI framework. It provides a component named edi.party.data.mixin (and a default implementation edi.party.data) that EDI backends can use to look up party information for an exchange record.
When the component is used, it takes the partner from the work context and asks the edi.party.helper model to build the party data, using the exchange record, the partner, a configurable name field and an optional language code. The result behaves like a read-only dictionary for backward compatibility.
A helper function is also available to find the right party data component for a given exchange record and partner, based on the backend's component matching rules.
Important: the module is deprecated. On server startup it logs a notice saying it will be removed and that the edi.party.helper model (or the EDIParty class) should be used instead, because those do not require component lookup. No menus, screens, buttons, reports, scheduled jobs or business rules are added by this module; it only exposes technical components and a utility function for other EDI modules.
Depends on
Required by other modules
Models and fields (2)
- edi.party.data · new model
- edi.party.data.mixin · new model
Text generated by AI (DeepSeek) from reading the Odoo 18.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: 3 confirmed, 6 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/edi-framework.
terminal Installation and usage
OCA documentation · Odoo 18.0Configuration
Source · Odoo 18.0ID numbers selection
See edi_party_helper_oca's configuration.
Name field
On the exchange type form, modify the advanced settings so that the work context of the component that is used (eg: generate) contains party_data_name_field. For instance:
components: generate: usage: my.generate work_ctx: party_data_name_field: name
Usage
Source · Odoo 18.0An handy util method is to retrive the component:
from odoo.addons.edi_party_data_oca.utils import get_party_data_component
component = get_party_data_component(exchange_record, partner)
data = component.get_party()
Deprecated: prefer edi_party_helper_oca's edi.party.helper model or its EDIParty class directly, they don't require any component lookup.
No verified information in OCA: Installation.
Installation 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.