odoo/odoo#189072
Created by fw-bot
Merged
at 6d53b9780dc3839ad0a53ca6fe4700c20848b8f9
Statuses:
- legal/cla: Contributor License Agreement check
- ci/runbot: Odoo Test Suite
- ci/upgrade_enterprise: Test upgrades for enterprise master
- ci/template: Contact runbot team on discord for help.
- ci/style: Optional style check. Ignore it only if strictly necessary.
- ci/security: Required security check. Can only be ignored by security team.
- label
- odoo-dev:saas-17.4-17.0-fix-peppol-write-override-las-PORo-fw
- head
- 19d714e86ba5f3e61df04a9a736626739881f9ac
- merged
- 1 year ago by Accounting, Laurent Smet (las)
| odoo/odoo | |
|---|---|
| 17.0 | #188985 |
| saas-17.2 | #189064 |
| saas-17.4 | #189072 |
| 18.0 | #189076 |
| saas-18.2 | |
| saas-18.3 | |
| saas-18.4 | |
| 19.0 | |
| master | #189231 |
[FW][FIX] account_peppol: Fix bad write override in case of multiple records
When the write is called with multiple companies (like the test TestAccountComposerPerformance), the values are updated with the values of the very first company. This will write a new peppol_endpoint on all companies. However, in this test, the very first company is a BE one but another is FR. Then, this write makes an inconsistency between the original FR EAS and the new BE endpoint.
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: #188985