In some case, we may have some unconventionals O2M like on ir.attachment. The O2M relation is done on res_id value.
This commit take them in consideration and avoid a traceback
Example use case:
- Install hr_fleet
- Set the employee_ids field of hr.employee as a tracking field
- Modify the user to not have permissions in Fleet
- Modify the name of an employee
TT51160
Example use case:
- Define the child_ids field of res.partner as tracking.
- Modify contact Brandon Freeman and leave parent_id empty (Azure Interior)
- No error should be displayed
TT51146
Example use case:
- Enable custom tracking in project.project
- Activate the task_ids field as custom tracking
- Create a project and assign it to a user (different from ours) and make it a note follower
- Create a task in the project
- The project message of the task tracking task will not be sent to the note followers
TT50676
Previously the bank_ids field was used but account adds messages in partner when
a related bank account is created/modified/deleted, causing tests to fail.
The user_ids field of res.partner is now used to avoid the side effect in tests
and the fake model is removed.
TT50571
Instead of complexe tracking throught the context
just track change and process the message at the end
using the precommit feature (the message are posted
just before commiting)
- track m2m simplify using native mail_thread and process them like text
- simplify code for track one2many
- avoid useless code on model not impacted by the tracking
For example on the product if you open the 'stock.putaway.rule'
you have activated the tracking on putaway_rule_ids
change on rule should be posted on the related product
- remove tracking_model (less model, less code, less issue)
- add automatic rule for default config (this avoid missing tracked field
after module installation)
OCA-git-bot
François Honoré
Víctor Martínez
Christopher Rogos
Christopher Rogos
Ivorra78
mymage
Weblate
oca-ci
Sébastien BEAU
Kev-Roche
Kévin Roche