In Odoo development, there are scenarios where a Boolean field needs to be saved automatically when an onchange method updates its value. This is particularly useful when the field is read-only and should reflect changes based on user actions on other fields.

Why Use force_save?
The force_save attribute in Odoo's XML is designed to handle such situations. By setting force_save="1", you ensure that the value of the Boolean field is saved to the database even if the field is read-only. This attribute becomes essential when you have an onchange method that alters the Boolean field based on changes in other fields, such as updating a status when a customer is selected or modified in a sales form.

Practical Application
Consider a scenario where you need to update a Boolean field named duplicate_found whenever a customer is selected in a sales order form. Normally, if the Boolean field is read-only, its new value might not be saved automatically. By using force_save="1", you can ensure that the field's updated state is recorded.

XML Configuration Example
Here’s an example of how you can configure this in your XML file:

<field name="duplicate_found" invisible="0" force_save="1"/>

The force_save attribute is a powerful tool in Odoo for managing read-only fields that need to be updated and saved based on dynamic changes. By leveraging this attribute, you can ensure that your data remains consistent and accurately reflects user interactions and automated processes.