@pokoli described correctly the problem. The default value is not send by the client because it did not changed and it is not filled because it is not a creation. And as all accounting values are stored on the same model, once it is created it is created with None value for all fields that are not modified.
This is the usual problem of global default. Should we store the default value and so it is no more inherited from the global configuration or we should consider None as not a real value and change it for the default global. As usual I do not like implicit behavior so for me we must have checkboxes to define if we use the default or not.
But now to fix the behavior for backport the multivalue storage model must use the default value of the party on creation. This should work by extending
multivalue_record. But maybe we can have a generic fix in
|2021-12-21 16:19:50||ced||set||messageid: <1640099990.8724058.JOVLLZ5XPVEHKSRP.email@example.com>|
|2021-12-21 16:19:50||ced||set||recipients: + pokoli, juanjogp|
|2021-12-21 16:19:50||ced||link||issue11077 messages|
Showing 10 items. Show all history (warning: this could be VERY long)