CiviCRM Community Forums (archive)

When you merge organization contacts, if they have individuals who are their current employees, the current employee field does not update correctly.  I just verified this on the 4.3 demo site.

This seems to be related to this issue http://forum.civicrm.org/index.php/topic,13555.msg58057.html#msg58057 which was fixed back in 3.2
(http://issues.civicrm.org/jira/browse/CRM-6184)

Here's the test case:

Create an Organization Record called "Test 1"
Create an individual Record "Mark Smith" current employer "Test 1"

Create another Organizational Contact "Test 2"
Create another individual record "Mark Johnson" current employer "Test 2"

Now use the deduplication feature to merge "Test 1" and "Test 2"  keeping "Test 1" as the existing contact and merging "Test 2" out of existence.

Look at the record for Mark Johnson.  You will be surprised to see his "current employer" is "Test 2", which does not exist in the database any more.  However, clicking on the highlighted link for "Test 2" actually takes you to the record for "Test 1".  I've left the test as is on demo if anyone wants to see this result.  http://drupal.demo.civicrm.org/civicrm/contact/view?reset=1&cid=125


(I haven't had time to verify yet on demo, but this came to my attention because we have organizational memberships with benefits flowing to indivudals who are employees and individuals who become employees of a member by means of a merge are not getting the appropriate membership.    I'm hoping if we resolve this issue it will cause the membership's to resolve correctly after a merge as well.)

I can see where to update the organization_name. That's pretty straightforward if I just force the sql statement.  But that wouldn't solve the  issue of memberships not being granted withdrawn properly based on the current employer relationship. 

I think that instead I'd need to find all the employees of the employer being merged out of existence and then loop through them running CRM_Contact_BAO_Contact_Utils::createCurrentEmployerRelationship($employeeid,$mainId);   

Would that cause the memberships to be adjusted properly, or is there something else I need to?