The Australian Ballet are keen to take advantage of the new Affiliations functionality to track the co-subscriber relationship – that of people booked for a subscription package but not the primary booker. We currently track co-subscribers through an Association.
We have been playing around with the idea of setting up a distinct Household type of ‘subscriber group'. We would then affiliate any individuals subscribing together into this group, including a ‘primary booker’ affiliate. Although we would maintain the transaction itself in the ‘primary booker’s’ individual account (a business decision reached across all orders and contributions), we would then be able to mirror the Ticket/Subscription History in the ‘subscriber group’ (household) and see via the header tree and within the Relationships tab who is part of that group.
We are also aware that any of the subscribers included in this group may also belong to (family) Households in their own right. I have attached our mudmap in case this explanation makes no sense!
I have a few questions;
· Has anyone come up with an elegant solution for tracking co-subscribers in V11?
· Is it possible to create multiple Household Constituent Types, which would allow for a ‘subscriber group’ type?
· Is it then possible for an Individual to be affiliated with multiple Household group types?
· Is it possible for an individual to be indicated as A1 or A2 on multiple Household groups?
Any assistance would be much appreciated!
Here are some quick answers to your questions:
Yes you can have multiple household constituent types.
Yes an individual can be affiliated with multiple households.
No a constituent cannot be an A1 or A2 on more than one household.
An individual can only have one primary affiliation, and a constituent cannot be set as an A1 or A2 unless the affiliation is primary. Also note that a non-primary affiliation does not trigger data visibility or inheritance, though I think that for what you want to do that doesn’t matter. A non-primary affiliate can still be displayed in the affiliate tree for the household, though, which it seems to be the primary thing you are looking for.
Kevin Sheehan
Senior Documentation & Learning Resources Specialist
Tessitura Network
+1 888 643 5778 x 329
ksheehan@tessituranetwork.com
Thanks Kevin,
Can I just confirm when you say 'a non-primary affiliation does not trigger data visibility or inheritance' that we would still see the Ticket and Subscription History in the group account if the Order itself sat in a non-primary affiliate's individual account?
Cheers
Amalia
No, you would not see that information on the household record if the affiliation is non-primary. Seeing any data from the individuals when looking at the household (and vice versa) only happens when the affiliation is primary. For a non-primary affiliation, all that is added to the household is the name of the individual, and that is only if the affiliation type used is set to Show With Group.
For full details on households and affiliations (and a sneak peek at the new v11 help system), see the Household Constituents topic.