Details
-
Type: Bug
-
Status: Done/Fixed
-
Priority: Critical
-
Resolution: Fixed/Completed
-
Affects Version/s: 4.7.4, 4.7.7
-
Fix Version/s: 4.7.9
-
Component/s: None
-
Labels:
-
Documentation Required?:None
-
Sprint:4.7.10 Merge
-
Funding Source:Contributed Code
Description
(Critical due to data loss)
When batch merging contacts via the interface you can 'flip' which contact is the duplicate record (and is therefore deleted). However, if you 'flip' and then batch merge (whether it is a 'safe' or 'forced' merge), the flip is not taken into account and the wrong contact is deleted.
Steps to recreate:
- Find and merge duplicates
- Run a rule
- Tick a pair that will conflict and choose 'batch merge'
- Then choose to 'flip' the contacts on the 'conflicts' screen, and 'force' merge them
- Notice that the master record has been deleted instead of the duplicate, the 'flip' operation was ignored.
Tests for this required. See CRM-18581
Attachments
Issue Links
- is supplemented by
-
CRM-19035 Batch merge deletes incorrect contact
- Done/Fixed