Setting up an event query to pull attribute information

Holly Holmes

I need a query that will pull the attribute shirt sizes and I am lost. 

John Heizer

Is it a Constituent Attribute?  Gift Attribute?  Participant Attribute?  And remember, Query is a grouping tool, not a reporting tool. You should use Export to get the data out of RE.

Holly Holmes

It is an event attribute.

John Heizer

Last time I checked events don't wear a t-shirt ?, so it doesn't make sense to make t-shirt size an event attribute. It should be tied to a person (Constituent), Gift (paying for the event), or Participant (someone registered for the event).

Holly Holmes

Thank you

Mark Guncheon

Is this for an event that has already happened?

Beth Romano

We also keep track of T-shirt size in events, the best way is to create a participant export with the attribute that you need, then in Crystal you should be able to group by that attribute.

Holly Holmes

This event has not happened yet. The problem I am having is trying to figure out the best operator to use with each query. 

Karen Diener

My suggestion is to add a participant attribute.  T--shirt size needs to be tracked for each participant.  Make the category "t-shirt size" and set the description to be a table with various t-shirt sizes in it.  That will be added to each participant who is registered for the event and needs a t-shirt.


It kind of depends on how your query will be used.  If you want to see all participants and their t-shirt size, your criteria will be all participants in the event and t-shirt size will be an output field.  You won't need an operator to select it as part of your criteria in this situation.  If you want to see how many people need medium shirts, then it becomes part of your criteria - all participants registered for the event and t-shirt size equals medium.


Does that help clarify?


Karen