diff options
| author | Thibault Delavallée <tde@odoo.com> | 2020-02-27 10:15:25 +0000 |
|---|---|---|
| committer | Thibault Delavallée <tde@odoo.com> | 2020-03-10 11:15:09 +0000 |
| commit | c6003af73409e2cd124f641fb7714fefa9dc8b01 (patch) | |
| tree | 751065a124cebdf7c94f2b9b3ce50235beb529bf /addons/web/static/src/js/fields | |
| parent | 5e4efef3ca3f2e9f02ec40c746c0d43aa3e97b79 (diff) | |
[IMP] event: set an explicit onchange on partner_id of registration
RATIONALE
Manual onchange is necessary because you spot an issue (or customer complains).
Automatic update through computed feild is only there to try to add missing
pieces of information but cannot decide which is the correct field value to keep.
SPECIFICATIONS
Keep an explicit onchange on partner_id. Rationale : if user explicitly
changes the partner in interface, he wants to update the whole customer
information. If partner_id is updated in code (e.g. updating your personal
information after registeration in website_event_sale) fields with a value
should not be reset as we do not know which one is the correct one.
How it should behave as following
* computed fields based on partner_id should only update missing
information. Indeed automated code cannot decide which information
is more accurate;
* interface should allow to update all customer related information
at once. We consider event users really want to update all fields
Tests are added to ensure behavior is not modified without notice.
LINKS
Task ID 2089156
Community PR odoo/odoo#42911
Diffstat (limited to 'addons/web/static/src/js/fields')
0 files changed, 0 insertions, 0 deletions
