Sale Partner Sale Contact on Project
This module extends Sale Partner Sale Contact to propagate the sale contact field to projects.
When a sale order with a sale contact creates a project (via service products), the contact person is automatically propagated to the project. This ensures the same named commercial contact (procurement manager, project lead, etc.) visible on the sale order and its invoices is also recorded on the resulting project, without affecting project or task addresses.
This allows you to:
Track the contact person for each project
Maintain consistency between sale orders and related projects
Display the sale contact on project forms
Table of contents
Usage
To use this module:
Install both Sale Partner Sale Contact and Sale Partner Sale Contact on Project
Create a sale order with a customer that has child contacts
Select a Sale Contact from the customer’s child contacts
Add a service product configured to create a project or task
Confirm the sale order
The created project will automatically have the same sale contact
You can also manually set or change the sale contact on any project form
The sale contact field is visible on the project form, right after the customer field.
Auto-switch behavior: If you select a contact person in the customer field and that person has a parent company, the system will automatically:
Set the customer field to the parent company
Set the sale contact field to the person you selected
This behavior only applies when the restriction modules (*_partner_id_company_only) are not installed.
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
Contributors
Simon Maillard (maisim) <simon@ogesta.fr>
Maintainers
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/sale-workflow project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Metadata
Release files for odoo-addon-sale-partner-sale-contact-on-project 16.0.1.0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo_addon_sale_partner_sale_contact_on_project-16.0.1.0.0.2-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_sale_partner_sale_contact_on_project-16.0.1.0.0.2-py3-none-any.whl |
Release files / odoo_addon_sale_partner_sale_contact_on_project-16.0.1.0.0.2-py3-none-any.whl
| Download URL | odoo_addon_sale_partner_sale_contact_on_project-16.0.1.0.0.2-py3-none-any.whl |
|---|---|
| Size | 28.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ea3cd33cdf0eeea6de983c70220f5bda41a65766c2fde6e9238b887e3fbc03e8
|
|
BLAKE2b-256 checksum How to use checksums |
5822ac732c540470633bfc9bdd83017228d30c5a9784ca9dd8d3a57de6378600
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for odoo-addon-sale-partner-sale-contact-on-project 16.0.1.0.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
