Details
-
Type: Bug
-
Status: Open
-
Priority: Minor
-
Resolution: Unresolved
-
Affects Version/s: 4.7, 4.7.10
-
Fix Version/s: Unscheduled
-
Component/s: Core CiviCRM
-
Versioning Impact:Patch (backwards-compatible bug fixes)
-
Documentation Required?:None
-
Funding Source:Needs Funding
Description
I have tested this on the demo server.
Setup
A contact with a custom field group (that can contain multiple values) that holds a contact reference field.
Example Scenario
- Andrew Adams has Barry Adams added as a contact reference in our custom field.
- Barry registers for an event and has a duplicate contact created.
- Barry Adams is merged with the duplicate, with the duplicate being marked as the primary contact (which gives Barry a new CID).
- Andrew Adams contact reference for Barry Adams still points to the old Barry Adams.
In some cases it may be difficult to determine which contact is the original. With that in mind we should not assume that the person doing the merge will choose appropriately.
I suggest that a duplicate merge should trigger a check for relationships and update any change in CID.