CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviEvent (Moderator: Yashodha Chaku) »
  • Duplicate participants
Pages: [1]

Author Topic: Duplicate participants  (Read 599 times)

goran

  • I post occasionally
  • **
  • Posts: 85
  • Karma: 3
Duplicate participants
May 20, 2010, 08:59:13 am
Hi to all,

While working on customizing some reports I noticed that I have entries in civicrm_participants that have identical contact_id and event_id (and all other fields, except register date).

I tried adding the same participant to an event and it was possible.

Is this a bug or are there reasons for allowing duplicate entries in events?

Best,
Goran


Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: Duplicate participants
May 20, 2010, 10:49:57 am

hey goran:

what is the payment status of these participants? we allow repeated registrations for participants (user requested feature) if they have not completed payment, i.e. in payment incomplete status (or pay later). i'm pretty sure this is configurable from participant status page (to allow which participants are considered to be part of event)

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

goran

  • I post occasionally
  • **
  • Posts: 85
  • Karma: 3
Re: Duplicate participants
May 21, 2010, 01:27:55 am
hey lobo,

these are offline registrations with no fee here (fee disabled, online registration disabled).

i think i see your point, here are some further thoughts (of lower priority :) ):

what's the use case for the incomplete ones? wouldn't it work for everyone if the incomplete registration were simply updated? between civicrm_contribution (through civicrm_participant_payment) for which you can have multiple payment records (incomplete, cancelled, ...) and participant statuses it seems that civicrm_participant could be kept semantically cleaner.

or was the idea that civicrm_participant is more like a log of event registrations with participant_status determining if they are counted as participants or are simply 'registration log' entries?

if the last one is true, then suggestions
- make some combination of status, event_id, contact_id unique on the table so that some integrity rules could be applied on the status workflow and clearer distinction between 'log of registrations' and 'list of participants' is made (for example for any participant status that has is_counted it should not be possible to have the same contact twice on the event)
- make it more clear on the event page/participant statuses in which case it is possible to have duplicates
- maybe offer two views of the participants on the event page - all registrations and list of participants
- civireport should then reflect this (maybe through easy way to select a set of final vs transitional statuses or countable vs all)

these comments are in essence mostly about semantics and documentation/descriptions/usability, as it was definitively unexpected for the end users here to have the same contact several times for an event.

best,
goran

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviEvent (Moderator: Yashodha Chaku) »
  • Duplicate participants

This forum was archived on 2017-11-26.