CiviCRM Community Forums (archive)

I have created custom data fields and a custom profile to add options to an event registration form.  That works fine, except for the fact that if I am looking to manually add an event registration to the person's record, the custom profile I created for events shows at the bottom.  This happens no matter which event I choose from the select menu.  Is there a way to hide these profile fields until the related event is selected?

Since there is an option to include (or not include) the custom profiles when setting up the event, it would be assumed that those fields created will not show by default at the bottom when manually adding an event registration.

Maybe I'm configuring something incorrectly, maybe this is the functionality or maybe this is just an overlooked bug.

I verify that this happens in 1.8, 1.9 and 2.0

The fields you're seeing when manually registering a participant for an event are the custom fields that you've defined as "Used For" Participants. The current functionality is to include custom fields "belonging" to a type of record on that record's admin input form.

You can adjust this behavior a bit by linking the custom data group to a specific Participant "role"  (e.g. Attendee, Volunteer, etc.). If you do this - then the custom fields will only appear on the admin input form after you've selected that specific Participant Role.  However, you can't currently include or exclude the fields based on the selected event.

Thank you for your reply.  I will work on a patch for this, depending on its complexity.

It only makes sense to me that the custom data fields show only when tied to the selected event.  Imagine having 5-10 events going through the system simultaneously, each with a set of custom fields.  The 'add event registration' page will become quite confusing.

If I'm able to provide a patch for this, is there a possibility of having it included in the next 1.9 and/or 2.0 release?

I'm engaging in some extreme thread necromancy - apologies if this isn't appropriate.

The fields you're seeing when manually registering a participant for an event are the custom fields that you've defined as "Used For" Participants. The current functionality is to include custom fields "belonging" to a type of record on that record's admin input form.

You can adjust this behavior a bit by linking the custom data group to a specific Participant "role"  (e.g. Attendee, Volunteer, etc.). If you do this - then the custom fields will only appear on the admin input form after you've selected that specific Participant Role.  However, you can't currently include or exclude the fields based on the selected event.

I'm currently running 3.4.8 for Drupal.  Is there any chance this behavior will be changed at some point so that custom data can be attached to a particular event rather than, or in addition to, just a record type?

Even linking the custom data group to a specific participant role won't work for us, because we need the custom data available for Attendee plus some custom roles we created.  Am I supposed to create four copies of the same custom data group, one for each role, and then FURTHER customize the roles to a particular event, just to keep unwanted custom data forms from other events from showing up when I want to edit a participation?

I don't think the current behavior is helpful - it would be nice if future versions could have a way to limit custom data to a particular event or multiple active events.

Thanks for any suggestions you can offer. 

Thank you!  The custom data set we have now is re-used from before the version update, and the "used for" can't be changed now.  But I see that if I create a new one, we'll get that option.  Awesome!