Memberships not being inherited by related contacts

Question

I'm working on a new CiviCRM implementation in Wordpress. I have imported contacts with an External ID in each record, imported contributions, memberships and relationships. The related contacts are not showing a valid membership by relationship and the Primary Member's membership record states "One contact is currently eligible to inherit this relationship."

I have tried deleting all records and reimporting in a different order; updating memberships; running update membership scheduled job.

I don't know where else to turn - I don't want to enter all of these manually.

Open to more ideas to solve the issue.

Thanks in Advance

Wordpress 4.5.3 CiviCRM 4.7.9

Answer 1

This is an on-again gone-again bug. At FF Towers we were never able to fix it and ended up writing an extension that did edit save on the membership to get it to work. Horribly hacky but day saved. Recommend more UTs.

Answer 2

I realize this question has been out here a long time, but I recently experienced a similar situation and solved it - my Civi version is 5.3.1 and I'm using it with Drupal version 8.6.3.

In my case, I had accidentally set up the Membership Type to be linked to Organizations, but had defined the Relationship to be "Employee of" rather than "Employer of". This meant that Civi went looking for contacts that the Organization was an "employee of" rather than contacts that the Organization was an "employer of" when it was time to create inherited Memberships.

There appears to be a display bug in Civi in which it detects that an Employer/Employee relationship does exist between the Organization and Individual even if the direction is reversed and it reports it as being "eligible." This seems to account for the reporting of eligible contacts but the failure to create the membership.

When I set up the membership type's relationship direction to use "Employer of," the membership inheritance began working. (In my case, I had to make a direct database update to the civicrm_membership_types table because Civi won't let you modify the membership type after memberships have been created. The update caused no data integrity issues for my situation. YMMV)

Or you can use this plugin to modify the relationship https://github.com/agileware/au.com.agileware.membershiprelationshiptypeeditor

Answer 3

Is the Relationship Type set properly in Administer > Civimember > Membership Types? Each Membership Type needs the specific kind of relationship (employer of, etc.) specified for inheritance to function correctly.

Answer 4

I've noticed recently that CiviCRM doesn't properly account for relationships that inherently operate in both directions (such as the spouse relationship).

For example, we noticed a wife who did not inherit the membership her husband owns, due to her being contact_a in the spouse relationship record. Deleting the spouse relationship and re-entering it from the husband's record fixes the issue, at least for the time being (some couples seems to alternate who donates for a membership, which means we'd have to delete and redefine their relationships every year).