CiviCRM Community Forums (archive)

I'm using PowerBase (3.4.4/Drupal 6).

I've just recreated this in the 3.4 demo site as well.

If I set up a custom membership (I called it Test Inherit Membership if you want to go to the site and look) where staff of an organization inherit their organization's membership, I also want that membership to end once their employment ends.

So My Company is a member of Magic Bus, and by extension, all the employees of My Company are members of Magic Bus (Fraddie Parker, Amar Jameson, etc.).  If then Fraddie Parker's employment ends with My Company, I don't want to extend Magic Bus membership benefits to Fraddie Parker.

If I manually edit the relationship so Fraddie Parker is NOT a current employee of My Company, Fraddie still is an active member of Magic Bus. 

Should I file this as a bug?

If I set up a custom membership (I called it Test Inherit Membership if you want to go to the site and look) where staff of an organization inherit their organization's membership, I also want that membership to end once their employment ends.

Membership end is calculated based on membership type and not on relationship end date.

So My Company is a member of Magic Bus, and by extension, all the employees of My Company are members of Magic Bus (Fraddie Parker, Amar Jameson, etc.).  If then Fraddie Parker's employment ends with My Company, I don't want to extend Magic Bus membership benefits to Fraddie Parker.

If I manually edit the relationship so Fraddie Parker is NOT a current employee of My Company, Fraddie still is an active member of Magic Bus.

Disabling relationship should also remove related membership for that contact. You can verify this behavior on demo.

HTh

Kurund
 

Why does ending the relationship by editing it not have the same effect? (I tested editing the relationship to be inactive in the demo site, and the membership does NOT end.) Disabling doesn't allow you to put in an end date, nor does it automatically make the end date today.

IMO having explicit disable action makes sense, this give more flexibility to the admin.

The word "disable" is confusing.  There are 3 ways to end the relationship (delete, disable, and edit manually) and it's not clear what the differences between each are (that you have to disable (not edit) to also disable the related membership).

I would say "Disable" is a shortcut if you only need to disable ( make it inactive) relationship without going to edit form. Delete and Edit are self explanatory.

Kurund

but, one of robyn's point is, when you edit a relationship and have an end date in the past (expired), the membership should be updated also (similar to disable)

In edit mode there is explicit checkbox to enable and disable relationship. So main question here would be do we want to automatically uncheck the checkbox if end_date is greater than current date. There are few other scenarios too. So I am not too sure about this approach.

Kurund