Clearly, as noted in the documentation and on the system table explanatory text, the preferred owner on a ticket order is the household (at least for an individual with a primary affiliation) but does anyone know why that is the case?
We're still learning about households versus individuals and how they pull up on lists.
Best,
Aileen
Hopkins Center, Dartmouth College
The purpose of the household object is to treat all of the household members’ activity as one thing. If you just wanted to know which people are married to each other, you could do that with Associations and not use households at all.
By letting the household own all of the activity, you can more easily query based on this activity in lists. For example, if you wanted to know constituents (households OR unaffiliated individuals) that ordered tickets to a specific event and made a contribution (no matter which household affiliate made each ticket purchases and contributions), your list criteria would be no different from if you were just querying individuals.
Also note that the Initiator field exists for you to indicate which individual household member was the one who placed an order or contribution.
Really helpful, Nick. Thank you! @michael.bodel@dartmouth.edu