[FIX] survey_record_generation: link to already created record at creation #29
Reference in New Issue
Block a user
No description provided.
Delete Branch "survey_record_generation-fix-other-record-overriding-computed-values"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
cf https://elabore.coop/odoo/project.task/6803 pour la demande fonctionnelle (il s'agit de pouvoir mettre un montant libre pour les abonnements générés par les réponses au sondage d'adhésion de Négawatt).
A NOT required "other_record" field was always set after the loop with a
write(), even when the linked record was already created. This late write
triggers the recomputation of stored computed fields depending on the
relation, overriding the values answered by the user.
E.g. with subscription_oca, sale.subscription.line price_unit depends on
sale_subscription_id.partner_id/pricelist_id: a free amount typed in a
numerical_box question (33) was replaced by the product price (20) when
the line was linked to its subscription.
Now the relation is given to create() when the linked record already
exists, so that the user's values are protected from recomputation. The
deferred write is kept for records created later.
When a question was not displayed (conditional question) or skipped, its
field was still given to create() with a None value. The field was then
emptied instead of keeping its default or computed value.
Since the link to an already created record is given at creation, this
also made sale.subscription.line price_unit equal to 0 when the "free
amount" question was not displayed, instead of the product price.
Fields without value are now left out of the values, which also allows
several conditional questions to fill up the same field (e.g. one list
of amounts per periodicity).
Assisted-By: Claude Opus 5.5 noreply@anthropic.com
@@ -1075,0 +1124,4 @@original_write = partner_class.writewritten_fields = []def spy_write(records, vals):Problème de design de checker le write ?