Skip to content

Do not store partner's has_lead_in_provisioning

Pelayo García requested to merge fix/do-not-store-has-lead-in-provisioning into master

CHANGELOG:

### Fixed
- [#827](https://gitlab.com/coopdevs/odoo-somconnexio/-/merge_requests/827) Do not store partner's has_lead_in_provisioning

Related card: https://trello.com/c/6hjLTAI0/1286-tiquets-duplicats-a-otrs

There's often a concurrency writing on DB that breaks the job create_ticket, trying to write down the attribute has_lead_in_provisioning (which we don't actually need saved on DB) while something else is being written on the partner instance.

2022-05-19 08:51:37,762 3061828 ERROR odoo odoo.sql_db: bad query: UPDATE "res_partner" SET "has_lead_in_provisioning"=true,"write_uid"=89,"write_date"=(now() at time zone 'UTC') WHERE id IN (29595)
ERROR: could not serialize access due to concurrent update
Edited by Pelayo García

Merge request reports