Answers.Body: <p>For your reporting perspective, it'll be basically the same.  However, the two options would make your registration process very different.  This should guide your decision.</p>
  
  <p>If you have a "one-room schoolhouse" model for your classes where one session includes advanced students taking it as Basketweaving 103 as well as new folks registered as Basketweaving 101, the participant custom field would allow for them to choose which one they're registering for.  From a logistical perspective, having a single event would make it easier to set a cap on total enrollment, see the full roster, and only have to set the location and time once.</p>
  
  <p>On the other hand, if you have Basketweaving 101 on Tuesday evenings, 102 on Wednesday evenings, and 103 on Saturday mornings, perhaps with different instructors, you'll want completely separate events.  You could set up event types for each, or you could have a single event type for all basketweaving and an event custom field for course number.  If you have a dozen or more separate courses, you'll probably want to put the course number in an event custom field so you don't have an overwhelming number of event types.</p>
  
  <p>You should be aware that if site visitors have the ability to view event custom fields, the custom field is displayed on the event info page.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-04-14T14:21:11.090Z
Answers.LastActivityDate: 2017-04-14T14:21:11.090Z
Answers.UserDisplayName: Andie Hunt
Body: <p>I've only been working with Civi for a couple of weeks ...</p>
  
  <p>Say we want to offer three workshops or classes:</p>
  
  <ol>
  <li>Basketweaving 101 </li>
  <li>Basketweaving 102 </li>
  <li>Basketweaving 103</li>
  </ol>
  
  <p>And later we want to be able to produce reports to do things like: "Show me everyone who has taken 101 and 102 but not 103."</p>
  
  <p>Would it be better, when creating a new event, to have an Event Type for each of these types of workshops, or alternatively to use the "Workshop" event type and have custom data fields that would allow the registrant to select 101, 102 or 103?</p>
  
  <p>I'm thinking that it may be nice to produce reports that show all workshops just by selecting one workshop type, which would argue for creating custom data fields.</p>
  
  <p>On the other hand, perhaps it's easier doing reporting on standard fields than custom ones, or there may be other "gotchas" with custom fields that I'm not aware of, which would argue for creating multiple Event Types.</p>
  
  <p>Or perhaps it doesn't really matter?</p>
  
  <p>Thanks in advance!</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-04-15T10:24:05.953Z
Comments.Text: Did you consider pricesets? See https://docs.civicrm.org/user/en/4.7/events/complex-event-fees/ .
Comments.UserDisplayName: Kainuk - CiviCooP
Tags: <civievent><custom-fields><civireport>
Title: Best practice: Multiple event types or custom data fields?
ThreadText: # Best practice: Multiple event types or custom data fields?
  
  (Asked by: username_0 on 2017-04-14)
  
  I've only been working with Civi for a couple of weeks ...
  
  Say we want to offer three workshops or classes:
  
  1. Basketweaving 101
  2. Basketweaving 102
  3. Basketweaving 103
  
  And later we want to be able to produce reports to do things like: "Show me everyone who has taken 101 and 102 but not 103."
  
  Would it be better, when creating a new event, to have an Event Type for each of these types of workshops, or alternatively to use the "Workshop" event type and have custom data fields that would allow the registrant to select 101, 102 or 103?
  
  I'm thinking that it may be nice to produce reports that show all workshops just by selecting one workshop type, which would argue for creating custom data fields.
  
  On the other hand, perhaps it's easier doing reporting on standard fields than custom ones, or there may be other "gotchas" with custom fields that I'm not aware of, which would argue for creating multiple Event Types.
  
  Or perhaps it doesn't really matter?
  
  Thanks in advance!
  
  **Tags:** civievent, custom-fields, civireport
  
  > **Comments:**
  > **username_1**: Did you consider pricesets? See https://docs.civicrm.org/user/en/4.7/events/complex-event-fees/ .  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2017-04-14. Score: 1
  
  For your reporting perspective, it'll be basically the same. However, the two options would make your registration process very different. This should guide your decision.
  
  If you have a "one-room schoolhouse" model for your classes where one session includes advanced students taking it as Basketweaving 103 as well as new folks registered as Basketweaving 101, the participant custom field would allow for them to choose which one they're registering for. From a logistical perspective, having a single event would make it easier to set a cap on total enrollment, see the full roster, and only have to set the location and time once.
  
  On the other hand, if you have Basketweaving 101 on Tuesday evenings, 102 on Wednesday evenings, and 103 on Saturday mornings, perhaps with different instructors, you'll want completely separate events. You could set up event types for each, or you could have a single event type for all basketweaving and an event custom field for course number. If you have a dozen or more separate courses, you'll probably want to put the course number in an event custom field so you don't have an overwhelming number of event types.
  
  You should be aware that if site visitors have the ability to view event custom fields, the custom field is displayed on the event info page.
  
  
  ---
  
  