Answers.Body: <p>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.</p>
  <p>In my case, I had accidentally set up the Membership Type to be linked to Organizations, but had defined the Relationship to be &quot;Employee of&quot; rather than &quot;Employer of&quot;.  This meant that Civi went looking for contacts that the Organization was an &quot;employee of&quot; rather than contacts that the Organization was an &quot;employer of&quot; when it was time to create inherited Memberships.</p>
  <p>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 &quot;eligible.&quot;  This seems to account for the reporting of eligible contacts but the failure to create the membership.</p>
  <p>When I set up the membership type's relationship direction to use &quot;Employer of,&quot; 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)</p>
  <p>Or you can use this plugin to modify the relationship <a href="https://github.com/agileware/au.com.agileware.membershiprelationshiptypeeditor" rel="nofollow noreferrer">https://github.com/agileware/au.com.agileware.membershiprelationshiptypeeditor</a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-11-17T15:16:51.107Z
Answers.LastActivityDate: 2021-02-23T20:13:04.130Z
Answers.LastEditDate: 2021-02-23T20:13:04.130Z
Answers.UserDisplayName: theta-fish
Answers.Body: <p>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.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-05-02T22:11:14.870Z
Answers.LastActivityDate: 2017-05-02T22:11:14.870Z
Answers.UserDisplayName: JohnFF
Answers.Body: <p>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. </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-08-08T16:09:56.373Z
Answers.Text: I set that up long before I imported the memberships. I even created a Test membership class with relationships, and imported a dummy file. Please ready my post fully - the system is recognizing that there are relationships that qualify for the inheritance, but it does not create that inheritance.
Answers.UserDisplayName: Barbara Forbes-Lyons
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-08-05T14:15:57.637Z
Answers.LastActivityDate: 2016-08-05T14:15:57.637Z
Answers.UserDisplayName: Sean MacGillivray
Answers.Body: <p>I've noticed recently that CiviCRM doesn't properly account for relationships that inherently operate in both directions (such as the spouse relationship).  </p>
  
  <p>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).</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-01-30T19:44:39.323Z
Answers.Text: This makes sense since when you set a Relationship Type to work for related Memberships you have to specify if you are starting from A or B, so yes, bi-directional relationships (where each A and B ends have same description) will get confusing
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-02-02T15:07:30.787Z
Answers.Text: @petednz BTW after more testing it seems I'm wrong about needing to define the relationship in the other direction to fix the issue - deleting the relationship and re-entering it from either spouse's record fixes the inherited membership. The several instances we found where the inherited membership was missing apparently had something to do with having been imported from SALSA.
Answers.UserDisplayName: Don Alejandro
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-01-30T13:53:56.037Z
Answers.LastActivityDate: 2020-01-30T13:53:56.037Z
Answers.UserDisplayName: Don Alejandro
Body: <p>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."</p>
  
  <p>I have tried deleting all records and reimporting in a different order; updating memberships; running update membership scheduled job.</p>
  
  <p>I don't know where else to turn - I don't want to enter all of these manually.</p>
  
  <p>Open to more ideas to solve the issue.</p>
  
  <p>Thanks in Advance</p>
  
  <p>Wordpress 4.5.3
  CiviCRM 4.7.9</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-09-05T11:32:13.317Z
Comments.Text: Have you tried edit/save on one of the Relationships to see if that triggers the inheritance?
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-09-05T20:42:53.657Z
Comments.Text: Yes, it does nothing. Only deleting the relationships and recreating them which is tedious and I'm not getting paid for because it should be working out of the box, so to speak.
Comments.UserDisplayName: Barbara Forbes-Lyons
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-09-05T23:23:12.597Z
Comments.Text: are you saying that if you already have the membership and then import the relationship it doesn't work, and if you do it v v it also doesn't work
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-09-07T13:19:53.953Z
Comments.Text: Yes - the memberships (and associated relationship types) were set up and the memberships were not inherited. I tried membership import first, then relationships AND the other way around. Neither time did the membership show up in the related contacts. Only be deleting the relationship and manually recreating it will cause the membership to be inherited. This is the first time that I've done this and it hasn't worked as it should. thanks for the comments!
Comments.UserDisplayName: Barbara Forbes-Lyons
Tags: <civimember><relationships>
Title: Memberships not being inherited by related contacts
ThreadText: # Memberships not being inherited by related contacts
  
  (Asked by: username_0 on 2016-08-04)
  
  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
  
  **Tags:** civimember, relationships
  
  > **Comments:**
  > **username_1**: Have you tried edit/save on one of the Relationships to see if that triggers the inheritance?  
  > **username_0**: Yes, it does nothing. Only deleting the relationships and recreating them which is tedious and I'm not getting paid for because it should be working out of the box, so to speak.  
  > **username_1**: are you saying that if you already have the membership and then import the relationship it doesn't work, and if you do it v v it also doesn't work  
  > **username_0**: Yes - the memberships (and associated relationship types) were set up and the memberships were not inherited. I tried membership import first, then relationships AND the other way around. Neither time did the membership show up in the related contacts. Only be deleting the relationship and manually recreating it will cause the membership to be inherited. This is the first time that I've done this and it hasn't worked as it should. thanks for the comments!  
  
  ---
  
  ## 4 answers
  
  ### Answer by username_2 on 2018-11-17. Score: 1
  
  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 by username_3 on 2017-05-02. Score: 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 by username_4 on 2016-08-05. Score: 0
  
  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.
  
  > **Comments:**
  > **username_0**: I set that up long before I imported the memberships. I even created a Test membership class with relationships, and imported a dummy file. Please ready my post fully - the system is recognizing that there are relationships that qualify for the inheritance, but it does not create that inheritance.  
  
  ---
  
  ### Answer by username_5 on 2020-01-30. Score: 0
  
  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).
  
  > **Comments:**
  > **username_1**: This makes sense since when you set a Relationship Type to work for related Memberships you have to specify if you are starting from A or B, so yes, bi-directional relationships (where each A and B ends have same description) will get confusing  
  > **username_5**: @petednz BTW after more testing it seems I'm wrong about needing to define the relationship in the other direction to fix the issue - deleting the relationship and re-entering it from either spouse's record fixes the inherited membership. The several instances we found where the inherited membership was missing apparently had something to do with having been imported from SALSA.  
  
  ---
  
  