Answers.Body: <p>You can also set the Group of Custom Fields to be collapsed on first view, which will impact on the back end 'add a participation record' (which use the Group of Custom Fields) but not on the front facing 'registration' forms (which use the Profile).</p>
  
  <p>This can help if you do have multiple Groups of Custom Fields showing on the same Entity or sub-Entity (eg Participant or Activity of Contact Type/sub-type)</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-24T21:20:49.217Z
Answers.LastActivityDate: 2016-05-24T21:20:49.217Z
Answers.UserDisplayName: petednz - fuzion
Answers.Body: <p>Ah those are not profiles but custom data sets/fields.</p>
  
  <p>Two tips:</p>
  
  <p>1) Make sure that the custom data sets that you create are more specific than just on Participants -> configure it to also narrow down to a specific event.</p>
  
  <p>2) Don't make the custom data fields within a custom data set required - but only make them required in the Profile - once you pull them in there. That way these fields are only required on pages that contain the profile.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-05-24T20:18:19.623Z
Answers.LastActivityDate: 2016-05-25T14:54:22.833Z
Answers.LastEditDate: 2016-05-25T14:54:22.833Z
Answers.UserDisplayName: KarinG - Semper IT
Body: <p>I have a site that has multiple different event types on it. Each of these event types have a different profile associated with the event.</p>
  
  <p>The client has back-end access to CiviCRM and when they try to manually register a person for an event it shows all of the profiles, not just the one associated with the event. Some of these fields are required fields, so the client then has to put something in them to finish the registration or save the edit.</p>
  
  <p>Is there a way to have all of the profiles that haven't been associated with an event type to not display in the back-end when editing or adding a registrant.</p>
  
Tags: <civievent><custom-fields><profile>
Title: Hiding Extra Profiles when Manually Adding/Editing Registrant
ThreadText: # Hiding Extra Profiles when Manually Adding/Editing Registrant
  
  (Asked by: username_0 on 2016-05-24)
  
  I have a site that has multiple different event types on it. Each of these event types have a different profile associated with the event.
  
  The client has back-end access to CiviCRM and when they try to manually register a person for an event it shows all of the profiles, not just the one associated with the event. Some of these fields are required fields, so the client then has to put something in them to finish the registration or save the edit.
  
  Is there a way to have all of the profiles that haven't been associated with an event type to not display in the back-end when editing or adding a registrant.
  
  **Tags:** civievent, custom-fields, profile
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2016-05-24. Score: 3 | Accepted answer
  
  Ah those are not profiles but custom data sets/fields.
  
  Two tips:
  
  1) Make sure that the custom data sets that you create are more specific than just on Participants -> configure it to also narrow down to a specific event.
  
  2) Don't make the custom data fields within a custom data set required - but only make them required in the Profile - once you pull them in there. That way these fields are only required on pages that contain the profile.
  
  
  ---
  
  ### Answer by username_1 on 2016-05-24. Score: 2
  
  You can also set the Group of Custom Fields to be collapsed on first view, which will impact on the back end 'add a participation record' (which use the Group of Custom Fields) but not on the front facing 'registration' forms (which use the Profile).
  
  This can help if you do have multiple Groups of Custom Fields showing on the same Entity or sub-Entity (eg Participant or Activity of Contact Type/sub-type)
  
  
  ---
  
  