Field Service - Sale Agreements
Integrates the Field Service and Sale Agreements modules, to:
- Propagate the agreement_id field from the Sales Order to the FSM Order
auto_awesome What this module does
AI-generated from the code · Odoo 19.0When a sales order linked to an agreement creates a Field Service order, the agreement is automatically carried over to that field service order.
This module connects sales agreements with field service work. It is installed automatically when the Field Service, Field Service Sale and Sale Agreements modules are all present, so users do not need to enable it manually.
The change is invisible on screen but affects how records are created: when a sales order is confirmed and a Field Service order is generated from it, the agreement selected on the sales order is copied onto the new field service order. This means the field service order keeps the same agreement reference as the sale, so staff can see which contract or agreement the on-site work belongs to without entering it again.
- The rule applies to the
sale.ordermodel and its preparation of field service order values. - It relies on the agreement field already provided by the Sale Agreements module on sales orders.
- No new menus, buttons, reports or scheduled actions are added.
Because the code only extends the value preparation step, there are no extra checks, restrictions or notifications. If a sales order has no agreement, nothing is copied. The module simply keeps the agreement information consistent between the sales order and the resulting field service order.
Models and fields (1)
- sale.order · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 19.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 19.0
Confirmed on 2026-11-03 in branch 19.0 of OCA/field-service.
terminal Installation and usage
No verified informationInstallation 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.