CRM-21727 Multirecord custom fields don't merge

    Details

    • Type: Bug
    • Status: Open
    • Priority: Important
    • Resolution: Unresolved
    • Affects Version/s: 4.7.29
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Versioning Impact:
      Patch (backwards-compatible bug fixes)
    • Documentation Required?:
      None
    • Funding Source:
      Needs Funding
    • Verified?:
      Yes

      Description

      Tested on demo.

      Create a set of multirecord custom fields. Create two contacts. Enter something in the new custom fields for each contact. Merge the contacts. The remaining contact does not get the custom field value from the deleted contact.

      This does not affect 4.7.23

        Attachments

          Issue Links

            Activity

            [CRM-21727] Multirecord custom fields don't merge
            Andrew Thompson added a comment -

            I verified that this issue exists on dmaster. As this causes data loss I think the priority should be raised to Critical.

            Andy Clark added a comment -

            Agree with Andrew on priority.  My customer fortunately noticed the data loss but is now worrying about whether they've missed other merges where records have been lost.   Should I cancel CRM-21731?

            Erik Hommel added a comment - - edited

            I have linked it to -------CRM-21731------- and set that to Won't Do as it is indeed a duplicate. I have changed the status to important. Will now try to replicate on 4.7.29 and check if I can see a cause quickly.

            • Created a new custom group for Individual and ticked the Does this Custom Field Set allow multiple records? and added a custom field 
            • added two Individuals with the same emailaddress and added 1 custom value in the created custom field for each contact (first and second)
            • when I use Contacts>Find and Merge Duplicate Contacts to find both contacts and merge them the second contact (the duplicate) is trashed and the first contact is saved. Even though I have ticked that the custom values should be merged, the first contact still has the first value and the record in the custom group table with value second is still linked to the id of the trashed duplicate contact.

            Not entirely sure without further debugging but it looks like CRM_Dedupe_Merger does not deal with many value custom fields.

            Andrew Thompson added a comment -

            CRM-21773 looks to duplicate this issue too. As that one has a patch in progress perhaps this issue could be closed?

              People

              • Assignee:
                Unassigned
                Reporter:
                Naomi Rosenberg

                Dates

                • Created:
                  Updated: