OdooWiki OCA HUB

Edi Backend Partner

edi_backend_partner folder_open OCA/edi open_in_new
Uncategorised License: LGPL-3

This module add the a "Partner" field in EDI backend, this can be useful in some situation in which a backend is restricted to only a given partner or to have another criteria to search edi backends.

auto_awesome What this module does

AI-generated from the code · Odoo 13.0

Adds a Partner field to EDI backends and shows a smart button on partner forms with the number of linked EDI backends, so you can see and open the backends restricted to a given partner.

This module links EDI backends to a specific contact. On the EDI backend form and list you now see a Partner field, so each backend can be tied to one partner.

On the contact (partner) form, a smart button labelled "EDI Backend" appears in the button box, but only when the partner has at least one linked backend and only for users in the EDI manager group. The button shows how many EDI backends are linked to that partner.

Clicking the button opens the related EDI backends: if the partner has several, you get a filtered list; if there is only one, Odoo opens its form directly.

The module extends the edi.backend and res.partner models and adds fields to the existing EDI backend form and list views and to the standard partner form. No new menus are created; the button reuses the existing EDI backend action.

Depends on

Models and fields (2)
  • edi.backend · extends an existing modelpartner_id
  • res.partner · extends an existing modeledi_backend_ids, edi_backend_count

Text generated by AI (DeepSeek) from reading the Odoo 13.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-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 1 confirmed, 8 with no information of 9 versions.

terminal Installation and usage

No verified information

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.

info

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.