CiviCRM Community Forums (archive)

are you saying that Inherited Memberships are not aware of whether the Relationship is current or is in the future.

If so i suspect this is something that has not yet been provided for.

In theory if a Relationship has a future date then imo it should be showing as Inactive - but it isn't necessarily set as Inactive which might be the fix that is required.

There is a scheduled job that finds Relationships with a 'past' date and sets them to Inactive - perhaps that could be extended to do the same for future relationships

But not sure how widely needed that would be. Do you have some resources (coding or $) to work on the solution?

if you create the relationship with a future date - and set it to inactive - does the inherited membership work properly

if so, as suggested above, i think the fix needs to be aiming at ensuring that relationships with future data are automatically treated as inactive - and that when the 'start date' arrives, the relationship needs to then get triggered to be 'active' - but i am not certain that that would be enough to then trigger the inherited membership

i don't suspect this has affected many others as the use case for 'start date' in the future is probably pretty rare

Do you have some resources (coding or $) to work on the solution?

I asked that as i doubt this will be high on the core teams list of issues since it seems like a rare situation