Skip to main content

Propagate archiving via partner_multi_relation relations

Project description

Beta License: AGPL-3 OCA/partner-contact Translate me on Weblate Try me on Runboat

Partner Multi Relation Archive Propagate

This module extends the behaviour of partner_archive_propagate to also propagate archiving and unarchiving via partner_multi_relation relations.

When a company is archived:

  • all related partners linked through relation types with propagate_archive = True are considered for propagation;

  • related partners without active users are archived and marked with propagated_from_id pointing to the company;

  • related partners linked to active users are skipped and listed in a message on the company.

When the company is unarchived, all partners that were archived because of it – whether through the partner hierarchy or through multi-relations – are restored automatically by the core partner_archive_propagate logic.

Non-company partners do not propagate via this module, even if they are involved in relations with propagate_archive = True.

Table of contents

Usage

  1. Install the following modules:

    • partner_multi_relation

    • partner_archive_propagate

    • partner_multi_relation_archive_propagate (this module)

  2. Configure relation types:

    • Go to Relation Types menu.

    • Create or edit a relation type.

    • Enable “Propagate archive” (propagate_archive) on the relation type(s) where archiving should cascade.

  3. Create relations:

    • Link a company partner to other partners using the configured relation types.

  4. Archive a company:

    • Use the “Archive Contact and Children” button (not the gear menu) to propagate archiving to related partners.

    • The wizard lists both hierarchy contacts and contact-type relation partners. Remove any row to exclude that partner from the operation.

    • All related partners reachable via relation types with propagate_archive = True will be treated like propagated descendants:

      • archived if possible,

      • skipped (and mentioned) if they have active users,

      • marked with propagated_from_id = <company>.

    Note: The gear (⚙) Archive action archives only the company itself and never propagates to relation partners, regardless of the Force propagation outside UI setting.

  5. Unarchive the company:

    • Unarchiving the company triggers the base partner_archive_propagate logic.

    • All partners (tree descendants or relation-based) that were archived because of this company (propagated_from_id) are unarchived and have the field cleared.

Bug Tracker

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.

Credits

Authors

  • Therp BV

Contributors

Maintainers

This module is maintained by the OCA.

Odoo Community Association

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:

ntsirintanis

This module is part of the OCA/partner-contact project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

File details

Details for the file odoo_addon_partner_multi_relation_archive_propagate-18.0.1.0.0.3-py3-none-any.whl.

File metadata

File hashes

Hashes for odoo_addon_partner_multi_relation_archive_propagate-18.0.1.0.0.3-py3-none-any.whl
Algorithm Hash digest
SHA256 d05411cad05b64c65363315f2c3dbd7633d367ad21340d0e9c4dcd1ba91dacca
MD5 c8417ca4f0668c4cd739e16ea6e7d803
BLAKE2b-256 f2c3c50e8cbc8deced850d5cc1000e79fef5b889c2d1e4a5981360e784327f74

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page