CiviCRM Community Forums (archive)

currently version 2.2.0
(upgraded from 2.1.0)
(which was upgraded from 2.0.0)

/civicrm/contact/view/participant?reset=1&action=add&cid=2&context=participant

When manually adding a participant to the system, custom data is showing up for the form, rather than a custom profile.  I cannot find a way to disable this.  Is this expected behaviour?  If it isn't, how can I troubleshoot and edit this?

When changing the selected event, the fee set and Registration Confirmation and Receipt both change to reflect the selected event, but the registration data does not.  How should I begin to troubleshoot this?

For clarification, it seems that I am having a comprehension issue rather than a code related one.

It doesn't seem that there's a way to link custom data to a specific event registration.

I have 8 events running, two of which share a common data set, and six others which share a 2nd custom data set.
When viewing from the back end(admin) contact pages:
https://example.org/civicrm/contact/view/participant?reset=1&action=add&cid=2&context=participant
or
https://example.org/civicrm/contact/view/participant?reset=1&action=add&cid=2&context=participant&mode=live

Both custom data sets show up beneath the registration information.  Should this be expected, or should the event be able to be tied to the data displayed?  If this currently isn't the case, it should be added to the 2.3 release or earmarked for the 2.4 release.

As a side note:

I can't seem to find any documentation that seperates the expected behaviour and differences between a back-end registration(administrator) vs a front end registration(end user).  I would be interested in committing to contribute documentation outlining the differences and the expected behaviour, after I finish learning and researching all functionality from both perspectives.

I've been following this project for about a year now, and it's come a long way.  It's far from perfect, but it's getting better every few months!  Keep up the great work.

As of 2.2, you have the option to link a custom data set which extends the Participant record to:
- participants in any event
- participants in a specific selected Event
- participants who have been assigned a specific Role (e.g. Attendee vs. Host vs. ....)

This gets you part of the way to solving your problem - but not completely since you can't currently share the custom data set between some (but not all) events. One potential future solution would be to support linkage via "Event Type". Then you could assign event type A to your first 2 events and event type B to your other 6 events.

Re: doc on differences between front and back end registration - a contribution in this area would be great.

As soon as I've finalized this registration flow, i'll have a lot more free time to start contributing back to the community.  This will be the first contribution that I will work on.

Thank you for all of your help, it's really appreciated.