If merging 2 contacts, one with reference, and another without, and being the target
one the contact without reference, the constraint is raised as the reference value
is copied before unlinking the other contact.
We avoid it disabling the constraint when merging.
Before this commit, the partner_ref_unique could be changed on the
company even if existing partners share the same internal ref.
Therefore, errors will appear afterwards as DB already contains
duplicates although the policy shouldn't allow it.
With this change, the error will appear as soon as the policy is
changed, so that the data must be fixed before activating the
constraint.
OCA Transbot updated translations from Transifex
OCA Transbot updated translations from Transifex
OCA Transbot updated translations from Transifex
OCA Transbot updated translations from Transifex
OCA Transbot updated translations from Transifex
This contraint is self-disabled when it detects by context that it is being used from the contact deduplicator.
Otherwise, the user cannot deduplicate a contact selecting the "good" one as the one without reference.
Anyway, in these cases, the check has no meaning, since it is to avoid duplicates and in this context we are currently removing them.
This module adds a priority field to contacts which can be configured within the configuration menu.
[UPD] LINT errors
fixed lint error, renamed test py file, added missing readme
[UPD] Removed unused file
removed incorrect py file
[FIX] wrong sequence val in test
Remove Test
[FIX] Data File Sequence
Fixed wrong sequence field name on data file.
[UPD] noupdate
Removed <data> element and moved noupdate into Odoo as suggested by reviewers.
[UPD] Reviewer Changes
Changes based on reviewer's suggestions
[UPD] Additional Review Changes
Additional changes requested from reviewers
[UPD] Sequence
Moved next sequence out of create method and into field def.
[UPD] Review Change
[FIX] LINT