Inactive Relationships Still Inherit Current Memberships?

[AudreyKate]

Hello all!

I'm setting up a Drupal/CiviCRM site for a professional organization with both individual and institutional memberships. For the institutional memberships, several individuals inherit the membership from the institution -- I've set this up with a custom relationship type, and it's working great.

However, even when I set an end date for the relationship, and the relationship comes up as "Inactive", the individual still inherits the organization's current membership (by relationship). I've done everything I can think of to fix this (I ran the Update Membership Record script, I deleted the relationship and recreated it with a past end date, etc). No luck.

I was able to recreate this on the demo site with inherited Household memberships. I created a household called "Household" with two members, "Headof Household" and "Childof Household." Even though "Childof Household" has an end date to the relationship of July 2, 1994, he still has an active membership -- he's still inheriting the current "Household" membership.

What am I missing here? Is there something simple I'm doing wrong?

Many thanks,
Audrey

[AudreyKate]

I wanted to update this in case it helps someone else having the same problem...

Apparently, the issue arises if you create the relationship AFTER you create the membership. In other words, if you're doing what I'm doing for this organization, and importing their data in batches. The organization record was imported first (and the org is a current member). The particular individual record that had a past relationship with them was imported later in that batch or in another batch. Because the membership was current when the relationship was CREATED in CiviCRM (ie imported), even though the relationship start and end dates had already past, the individual record inherited the current membership. When I deleted the organizational membership and re-created it with all the same data, the individual record no longer showed a current inherited membership. I was able to recreate this on the demo site.

This seems like it would offer a challenge if you wanted to add archival information to your database or were just looking, like I was, to import data in batches. But that's the solution to the problem -- you can't create or import records that have past-dated relationships with a current household member or organizational member -- because if there's a current membership, or they'll inherit it, too!

[Andrew Perry]

There has been a patch made in 3.4.1 that may fix this behaviour. See http://forum.civicrm.org/index.php/topic,19707.0.html

If you try it and it works, please let people know here.

Andrew